How Apps are made?
| Apple | |
|---|---|
| iOS | Android |
| Apple App Store | Google Playstore |
| Swift UI | Jetpack compose |
It started with a mistake. In 2012, Mark Zuckerberg publicly admitted that Facebook's biggest blunder was betting too much on HTML5 for their mobile app — it was slow, unstable, and users hated it. They needed native performance but didn't want to maintain two completely separate codebases for iOS and Android.
Inside Facebook, an engineer named Jordan Walke (the same guy who created React for the web) had been experimenting with something wild — generating native iOS UI elements from a background JavaScript thread. He built a prototype, and Facebook organized an internal hackathon in summer 2013 where Jordan teamed up with Christopher Chedeau, Ashwin Bharambe, and Lin He to prove the concept could actually work as a full mobile framework.
The hackathon prototype was convincing enough that Facebook turned it into a real project. In January 2015, they previewed React Native publicly at React.js Conf. By March 2015, React Native for iOS was open-sourced on GitHub, and Android support followed in September 2015.
The pitch was simple and revolutionary: "Learn once, write anywhere." If you already know React (which millions of web developers did), you can now build real native mobile apps — not webview wrappers, actual native UI — using the same mental model and JavaScript. One codebase, both platforms, native performance.
It exploded. Within a year it was one of the most starred repos on GitHub, and major companies started adopting it.
Social & Communication:
Shopping & Payments: