React Native: Buy One, Get One Free
summary
Three production apps (combined >1M downloads) use React Native in three different architectures: a full React Native app, native-heavy with RN for article rendering, and a native-first app with ~90% TypeScript. Navigation uses native navigation by launching activities/view controllers that each host a React Native root view, enabling per-screen native swaps. Switched from Firebase to REST after realtime updates caused background screens to re-render; fixed performance by returning false in shouldComponentUpdate. Replaced RN Image with FastImage. Upgrades and native tooling (Swift/Kotlin) are painful.
AI-written summary · about
chapters (13)
- 0:00Introduction and overview
- 2:54Why React Native matters
- 9:43Navigation challenges and solutions
- 13:19TypeScript and performance fixes
- 17:51Android vs iOS differences
- 18:55Upgrading React Native pain points
- 20:22Architecture approaches in projects
- 22:31Code sharing benefits
- 24:21Developer experience perks
- 25:47Android first recommendation
- 27:35Team and client alignment
- 29:03Development time savings
- 30:30Final thoughts and Q&A
related talks
13mIntegrating React Native with Native Infrastructure
45mReact Native: Things we learned the Hard Way
28mShould I use React Native too?
25mReact Native in Practice
07mFrom Native to React Native
01h 01mReact Native: A Better Way to Do Mobile
31mUsing React Native to ship fast and navigate performance improvements
26mReact Native is the new black