The performance myths of React Native
summary
Compares real apps to native by number and tooling: builds a sample app "Let's spend your money" with lists, charts and animations and measures CPU, memory, startup and FPS; uses FlatList not ScrollView and memoization to stop re-renders, removes console logs, and profiles with React Profiler and Flipper; chooses Reanimated v3 and Lottie for smooth animations; discovers Android device testing matters (global Android share ~72%), and a glucose‑camera feature proves JavaScript too slow so bridging to native fixes the lag.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 2:33Speaker and resources
- 4:48React Native myths
- 6:05Spend Your Money demo
- 8:14Measuring performance
- 10:44FlatList efficiency
- 12:30Optimizing re-renders
- 16:26Console logs impact
- 17:27Animations in React Native
- 20:44Android vs iOS testing
- 23:13Profiling tools
- 24:58Background tasks
- 25:40Native vs React Native
- 27:53Low-end device testing
- 28:55Convincing friends
- 29:38Final tips
related talks
24mThe Performance Myths of React Native apps
26mMeasuring and Improving React Native Performance
39mPerformance issues: the usual suspects
11mTips for Building Successful React Native Apps
54mReact Native Better Than Native
21mNative, React Native, Flutter and More
30mMaking React Native Fast & Lean
27mBuilding high quality mobile apps with React Native
