React Native Performance & State Management — Issues We All Face (And How to Fix Them)

If you've been working with React Native, you already know — the magic of writing one codebase for both iOS and Android comes with its own set of headaches. Especially around performance and state management.

Let me break down the most common issues I've seen (and personally struggled with):

1. Unnecessary Re-renders

This is the silent killer of React Native performance. Every time state changes — even slightly — your component tree can re-render unnecessarily.

Fix: Use React.memo(), useMemo(), and useCallback() wisely. Don't skip dependency arrays in hooks. Profile with Flipper or React DevTools.

2. State Management Chaos

As apps grow, passing props 5 levels deep (prop drilling) becomes a nightmare. And global state tools like Redux, when misused, make things worse — not better.

Fix: Use Context API for small apps. For complex state, Zustand or Jotai are lighter alternatives to Redux. Keep state as local as possible.

3. Memory Leaks

Forgetting to clean up subscriptions, event listeners, or async calls when a component unmounts — this causes memory leaks and crashes on real devices.

Fix: Always return a cleanup function from useEffect. Use AbortController for fetch calls.

4. Async State Bugs

Setting state after a component unmounts, or racing conditions in async functions — these bugs are hard to catch and harder to debug.

Fix: Track component mount status with a isMounted ref, or cancel async operations properly.