Optimizing React Native Performance
summary
Shows that React Native startup really is about module loading not just JS size: 78 ms for initialized core, a heavy navigator can add 250 ms before any component mounts, and apps sometimes pull in five versions of lodash. Recommends isolating side effects, using dynamic import for navigator screens, avoiding barrel re-exports, measuring with DataDog, trimming redundant dependencies, and using why-did-you-render and ESLint/react-compiler checks; the incremental fixes are small, measurable, and actually reduce perceived load without rewriting the app.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:08Who this talk is for
- 2:32Performance matters
- 6:03React Native bottlenecks
- 9:19Module loading process
- 11:28Isolating side effects and lazy loading
- 14:19Lazy imports in React Navigation
- 16:30Avoiding barrel files
- 18:36Reducing dependencies
- 21:30Network optimizations
- 23:59Unnecessary renders and animations
- 25:04Systemic changes and new architecture
- 26:00Q&A
related talks
30mMaking React Native Fast & Lean
21mJavaScript, React Native and Performance
39mPerformance Does Matter - Making Your React-Native App Fast
24mThe Performance Myths of React Native apps
24mOptimising React Native "Tools and Tips"
25mReact Native Performance - Take 2
23mPractical Performance for React Native
31mThe performance myths of React Native