The React Native performance playbook for growing apps

Performance work should begin with a reproducible user journey and a clear baseline. Profile startup, navigation, scrolling, and the interactions customers repeat most often.

A frame drop in a rarely used screen matters less than hesitation in the core workflow. Let product usage determine where engineering effort goes first.

Large list updates, image decoding, and synchronous data transformations can compete with animation and touch handling. Move work out of critical interactions and render only what the user can see.

• Use stable keys and memoized row components for large lists.
• Pre-size images and request only the resolution the device needs.
• Defer nonessential work until navigation transitions complete.

Performance regressions are easier to prevent than to diagnose after customers report them. Track startup time, interaction latency, bundle size, and crash-free sessions as release criteria.