The Performance Myths of React Native apps
summary
Claims that React Native is inherently slow get tested with real builds: a large e‑commerce-style app and a glucose‑scanner prototype where a native camera bridge is required. Tools and tactics used include FlatList/SectionList for lazy rendering, profiling in production with Flipper/Xcode/React Profiler, removing console logs, and choosing Reanimated and Lottie for off‑thread animations. Finds that overusing memoization can hurt more than help, that measuring CPU/memory and testing on low‑end devices matter, and that hitting a 60 fps target yields noticeably smoother UX.
AI-written summary · about
chapters (7)
- 0:00Start
- 0:06Checklist for a Great Talk
- 5:28Criteria for Measuring Performance
- 6:083 important criteria for Performance
- 12:07Remove unnecessary console logs
- 15:22Turn off Animations on low data mode or low memory
- 17:26Tools: Flipper, Xcode & React Profiler
related talks
31mThe performance myths of React Native
26mMeasuring and Improving React Native Performance
11mTips for Building Successful React Native Apps
39mPerformance issues: the usual suspects
23mPractical Performance for React Native
30mMaking React Native Fast & Lean
24mOptimising React Native "Tools and Tips"
29mPerformance Limitations of React Native and How to Overcome Them