an iOS Developer's Opinion of React Native
summary
Claims React Native is not a hybrid but renders native UI views while JavaScript runs on a separate thread and communicates over a serialized bridge bottlenecks that cause performance pain for animations and high-frequency events. Teams ship cross‑platform features (Instagram’s Promote, Eaze consumer + driver apps), use CodePush for over‑the‑air JS updates, and wrap Objective‑C/Swift modules when needed. Ramp times vary: experienced web devs ~1–2 weeks, experienced native devs ~1–3 months to be productive; CocoaPods and Android fragmentation remain common headaches.
AI-written summary · about
chapters (8)
- 0:00Introduction and background
- 2:29What is React Native
- 9:41How React Native works
- 12:29Case for React Native
- 17:27Advantages for native devs
- 21:18Case against React Native
- 28:00Should you use React Native?
- 29:25Summary and conclusion
related talks
53mHow React-Native shapes the way we think about native apps
01h 01mReact Native: A Better Way to Do Mobile
27mBuilding high quality mobile apps with React Native
26mReact Native is the new black
31mReact Native in 40 minutes
12mReact to React Native: How Hard Could It Be?
41mReact Native - A native love story
52mWhy you should use React Native for your next mobile app
