How to actually improve the performance of a React Native app?
summary
Argues that React Native performance is a process to fix, not a single tweak, and recommends the DMACC workflow (Define, Measure, Analyze, Improve, Control) with concrete tools: react profiler, react-native-performance and native profilers (Xcode Instruments / Android Profiler) to show most issues live on the JS side, measure on release builds, and account for measurement variation. Recommends CI regression detection with reassure, and ongoing monitoring via Firebase Performance or Sentry; improvements are usually incremental and require prioritized, data-driven fixes.
AI-written summary · about
chapters (18)
- 0:00Start
- 1:07How To Actually Improve the Performance of a React Native App
- 4:59Conclusions
- 7:48Defined Phase
- 9:30User Path Analysis
- 11:01Measure Phase
- 12:11React Profiler
- 12:34React Native Performance
- 13:13Profilers
- 14:02Flipper
- 14:30Measurement Variation
- 16:01The Analyze Space
- 16:29Brainstorming
- 16:52Cause and Effect Diagram
- 17:06Fisherman Diagram
- 19:03Hypothesis Testing
- 21:33The Control Phase
- 21:48Control Phase
related talks
25mReact Native Performance - Take 2
24mOptimising React Native "Tools and Tips"
24mThe Performance Myths of React Native apps
30mMaking React Native Fast & Lean
26mMeasuring and Improving React Native Performance
23mPractical Performance for React Native
31mThe performance myths of React Native
26mOptimizing React Native Performance