Why you should use React Native for your next mobile app
summary
Argues that React Native delivers native-feeling mobile apps while letting teams reuse web React skills, claiming 80–100% shared code between iOS and Android and consistent 60 FPS interactions by offloading heavy work to native threads via a JSCore+bridge architecture. Demonstrates quick prototyping with Expo Snack + Expo app, native navigation/animation libraries (Wix react-native-navigation), using NPM packages and react-native link for native modules, and sending small fixes via Microsoft-style over‑the‑air updates.
AI-written summary · about
chapters (11)
- 0:00Start
- 8:50WEB ECOSYSTEM
- 10:09WHY NOT USE NATIVE?
- 10:47OTHER SOLUTIONS - HYBRID
- 12:17GETTING STARTED #1 - EASY
- 14:10GETTING STARTED #2
- 14:57GETTING STARTED 2
- 15:10GETTING STARTED #3 - HARDER
- 34:33DEBUGGING
- 35:20EMBED OTHER PEOPLE'S NATIVE CODE-REACT NATIVE LINK
- 38:18Embed Web Views!
related talks
53mHow React-Native shapes the way we think about native apps
25mReasons to give React Native a(nother) try
44mReact Native: how to succeed with your mobile app
01h 01mReact Native: A Better Way to Do Mobile
54mReact Native Better Than Native
27mBuilding high quality mobile apps with React Native
26mReact Native is the new black
17mDispatches from React Native