React Native in Practice
summary
Production React Native work reduces to concrete surprises: apps used by a million users break from small repeated choices; a reused card that grows into 23 props, 60 lines becomes unmaintainable; lists that use an inline render + Math.random key cause Android feeds to thrash; skipping upgrades turns a 0.68 → 0.79 upgrade into six weeks of Metro, Gradle and native-module fixes. Expect profiling on midrange Android, dependency audits, split components, feature-flag expiries, and scheduled boring upgrades.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:06React Native breaks in prod
- 3:45Component reuse pitfalls
- 8:03Performance in feeds
- 12:44Cost of React Native upgrades
- 17:17Ownership of undocumented code
- 20:32Third-party library crashes
- 24:18Conclusion and key takeaways
related talks
45mReact Native: Things we learned the Hard Way
24mReact Native - Success case study
24mThe Performance Myths of React Native apps
31mThe performance myths of React Native
27mA Successful Case of Using React Native in Production
44mBest Practices to Build Scalable React Native Apps
33mReact Native: Buy One, Get One Free
41mReact Native - A native love story
