React Native: A Better Way to Do Mobile
summary
Argues that React Native reduces UI complexity by rendering real platform widgets from JavaScript/JSX, moves image decoding to threads via Fresco, and separates layout on a shadow thread so apps stay responsive; Facebook teams double framework speed with optimizations and ship parts of big apps like Events, Ads Manager, Discord and Discovery VR; native modules act as an escape hatch (example map and native list via ComponentKit), updates deploy over the air with CodePush, and development is fast with hot module reloading and ~80–87% shared code in some projects.
AI-written summary · about
chapters (24)
- 0:00Introduction
- 0:45What is React Native
- 3:43Why React Native
- 4:11Native Components
- 8:39The Uncanny Valley
- 13:01Threading
- 18:14WebView Performance
- 24:13React Native Performance
- 27:35Animated API
- 30:18Integration extensibility
- 32:32What if Apple or Google releases new APIs
- 33:08How often should I use React Native
- 35:23Advantages of React Native
- 42:12React Native Ideas
- 43:58Debug
- 44:40Testing
- 45:48NPM
- 50:11Legal Support
- 50:53License Agreement
- 51:36What happens if Facebook drops support
- 53:29Can you build a React Native app today
- 54:06How much code will I be able to share
- 56:58Should we use Xamarin
- 58:14When should we use React Native
related talks
27mBuilding high quality mobile apps with React Native
39mReact Native - Unleash the power of React in your device
30mReact Native
26mReact Native is the new black
54mReact Native Better Than Native
52mWhy you should use React Native for your next mobile app
25mThe state of React Native
46mReact native and its impact on android development