React Native Performance Checklist: 10 Fixes That Make Apps Feel Fast
A slow React Native app almost always comes down to the same few causes: too much work on the JavaScript thread, too many re-renders and heavy lists or images. Work through this checklist in order, measuring before and after each change.
1. Measure first
Use the React DevTools Profiler to see which components re-render and why, and the performance monitor in the dev menu to watch JS and UI frame rates. Optimising without measuring usually moves the problem instead of fixing it.
2. Use FlatList or FlashList for long lists
Never render long lists with ScrollView and map(). FlatList virtualises rows so only visible items exist in memory. Give it a stable keyExtractor, set getItemLayout when rows have a fixed height, and tune windowSize and initialNumToRender. FlashList can go further for very large lists.
3. Stop unnecessary re-renders
- Wrap row components in React.memo.
- Memoise callbacks with useCallback and derived values with useMemo, but only where profiling shows a benefit.
- Keep state as local as possible so a change does not re-render the whole screen.
- Avoid creating new object or array literals in props on every render.
4. Optimise images
Serve correctly sized images, prefer WebP, and use a caching image component such as expo-image. Decoding a 4000px photo into a 60px avatar is a common hidden cost.
5. Keep the JS thread free
Heavy loops, large JSON parsing and synchronous storage reads block touch handling. Move work off the critical path with InteractionManager.runAfterInteractions, batch updates and paginate API responses.
6. Run animations on the UI thread
Use React Native Reanimated so animations run on the UI thread and stay smooth even when JavaScript is busy. Animate transform and opacity rather than layout properties.
7. Reduce startup time
- Enable the Hermes engine (default in modern Expo and React Native).
- Lazy-load rarely used screens and heavy libraries.
- Avoid doing network calls and large storage reads before the first screen renders.
8. Trim your bundle
Remove unused dependencies, import only the functions you need from utility libraries and check bundle size regularly. Smaller bundles load and parse faster on low-end devices.
9. Test on real, low-end devices
A flagship phone hides problems. Test release builds, not just development builds, on an older Android device before you ship.
10. Monitor in production
Add crash and performance monitoring so you catch regressions from real users instead of waiting for bad reviews.