Performance issues: the usual suspects
summary
A dummy app with common React Native slowdowns is built and fixed live using React DevTools, Hermes profiler and Android Studio traces plus a Flipper CLI that runs automated 10-iteration measurements. Changes cut JS thread blocked time from ~9s to <4s then to ~1.4s, dropped a 400ms tweets render to ~0.4ms by extracting countdown and switching to Jotai atoms, removed a costly date parse in filterTweets, enabled lazy tabs, stopped a background skeleton animation and replaced a WebView GIF, raising the score to 96/100.
AI-written summary · about
chapters (11)
- 0:00Introduction to performance issues
- 2:27Measuring performance with CLI tool
- 9:12Optimizing component re-renders
- 13:32Comparing performance metrics
- 15:45Investigating app startup
- 20:44Single responsibility principle
- 23:13Lazy rendering of tabs
- 25:21High algorithmic complexity
- 31:54UI thread performance issues
- 35:04Heavyweight views impact
- 38:20Summary of fixes
related talks
26mMeasuring and Improving React Native Performance
24mOptimising React Native "Tools and Tips"
23mPractical Performance for React Native
24mThe Performance Myths of React Native apps
31mThe performance myths of React Native
30mMaking React Native Fast & Lean
39mPerformance Does Matter - Making Your React-Native App Fast
25mReact Native Performance - Take 2
