Measuring and Improving React Native Performance
summary
A Flipper plugin records JS and UI FPS over time and automates runs with ADB shell input swipe on a Samsung J3 2017 to reproduce low-end behavior; React DevTools flame charts and Hermes/IDE profilers pinpoint expensive renders. Fixes include memoize renderItem to stop unnecessary rerenders, disabling react-native-snap-carousel loop that inflated slides, and replacing nested FlatList carousels with a ScrollView paging strategy. Measured score rises roughly 40→90, JS “dead” time drops from ~4s to ~0s.
AI-written summary · about
chapters (10)
- 0:00Introduction and setup
- 1:48What makes an app performant
- 3:58React Native performance basics
- 5:24Measuring performance tips
- 7:15Real-world case study
- 9:03Analyzing with React DevTools
- 13:18Fixing performance issues
- 18:40Iteration three and deeper fixes
- 20:24Final optimizations
- 23:31Summary and next steps
related talks
39mPerformance issues: the usual suspects
24mThe Performance Myths of React Native apps
31mThe performance myths of React Native
23mPractical Performance for React Native
24mOptimising React Native "Tools and Tips"
25mReact Native Performance - Take 2
39mPerformance Does Matter - Making Your React-Native App Fast
22mYou can go EVERYWHERE but I can go FAST - performance case study
