Tips for Building Successful React Native Apps
summary
Simulators hide platform bugs; testing on real devices across many Android models reveals crashes and performance regressions. The native stack navigation performs better, caching via polo client reduces requests and simplifies query updates, and FlatList or Shopify's flash list handles big lists. Removing debug output with a Babel plugin to remove console logs prevents JS-thread bottlenecks. Debugging uses flipper for network, logs and DB inspection.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:34Testing on real devices
- 2:36Web vs React Native styling
- 3:40Navigation libraries
- 4:41Performance on slow networks
- 6:07Removing console logs
- 7:10Optimizing large lists
- 8:17Handling offline mode
- 9:44Debugging with Flipper
related talks
24mThe Performance Myths of React Native apps
31mThe performance myths of React Native
25mReact developers in a wild world of native apps
25mReact Native in Practice
44mBest Practices to Build Scalable React Native Apps
26mContributing To React Native Is Easy
44mReact Native: how to succeed with your mobile app
26mMeasuring and Improving React Native Performance
