State management comparison in React Native - Build, Publish & Deploy

Build & Publish - State management comparison

Performance Impact

Choosing the right state management affects your app's smoothness and battery use. Simple state (like React's useState) updates fast and uses little memory, ideal for small apps. Complex libraries (Redux, MobX) add overhead but help manage big apps. Poor state choices can cause slow UI updates and lag, dropping below 60fps.

Optimization Tips

To keep 60fps, update only necessary components. Use memoization (React.memo) to avoid re-rendering unchanged parts. For Redux, use selectors to limit updates. Avoid deep nested state changes; flatten state shape. Batch state updates to reduce renders. Profile with React DevTools to spot slow updates.

App Size and Startup Time

Lightweight state (React hooks) adds almost no size. Libraries like Redux or MobX increase bundle size by a few hundred KB, which can slow startup slightly. Use code splitting and lazy loading to reduce initial load. Tree shaking helps remove unused code from state libraries.

iOS vs Android Differences

State management libraries work the same on both platforms in React Native. However, Android devices vary more in memory and CPU, so heavy state libraries may impact Android performance more. iOS tends to have more consistent hardware, so performance is more predictable. Always test on real devices for both.

Store Review Guidelines

Neither Apple App Store nor Google Play restrict state management choices. But apps must be responsive and stable. Excessive memory use or crashes from bad state handling can cause rejection. Follow best practices for smooth UI and low battery use to pass reviews easily.

Self-Check

Your app takes 5 seconds to load this screen. What's likely wrong?

• Too many unnecessary state updates causing slow rendering.
• Heavy state libraries loaded upfront without code splitting.
• Deep or complex state causing slow reconciliation.
• Not using memoization or selectors to limit renders.

Key Result

Choosing the right state management in React Native balances app smoothness, memory use, and bundle size. Simple hooks suit small apps for 60fps performance, while libraries help scale but need optimization to avoid lag and slow startup.

Practice

1. Which React Native state management method is best for simple, local component state?

easy

A. Redux

B. useState

C. Context API

D. MobX

Solution

1. Step 1: Understand local state needs

   Local state means data used only inside one component, like a toggle or input value.

2. Step 2: Match state method to simplicity

   useState is designed for simple, local state inside functional components.

3. Final Answer:

   useState -> Option B

4. Quick Check:

   Simple local state = useState [OK]

Hint: Simple local state? Use useState hook [OK]

Common Mistakes:

• Choosing Redux for simple local state
• Confusing Context API with local state
• Thinking MobX is simpler than useState

2. Which of the following is the correct syntax to declare a state variable using useState in React Native?

easy

A. state count = useState(0);

B. let count = useState(0);

C. var count, setCount = useState(0);

D. const [count, setCount] = useState(0);

Solution

1. Step 1: Recall useState syntax

   The correct syntax uses array destructuring: const [value, setter] = useState(initialValue);

2. Step 2: Check each option

   const [count, setCount] = useState(0); matches the correct syntax exactly.

3. Final Answer:

   const [count, setCount] = useState(0); -> Option D

4. Quick Check:

   useState syntax = const [value, setter] = useState(initial) [OK]

Hint: useState always returns [value, setter] array [OK]

Common Mistakes:

• Using let or var instead of const
• Not using array destructuring
• Trying to declare state with 'state' keyword

3. What will be the output of this React Native code snippet?

const [count, setCount] = useState(0);
setCount(count + 1);
setCount(count + 1);
console.log(count);

medium

A. 0

B. 1

C. 2

D. Error

Solution

1. Step 1: Understand state updates are asynchronous

   Calling setCount twice with count + 1 uses the same stale value of count (0), so both setCount calls set count to 1.

2. Step 2: Check console.log output

   console.log(count) runs before state updates complete, so it logs the initial value 0.

3. Final Answer:

   0 -> Option A

4. Quick Check:

   State updates async, console logs old value [OK]

Hint: State updates are async; console logs old value [OK]

Common Mistakes:

• Expecting count to be 2 immediately
• Thinking setCount updates synchronously
• Ignoring that console.log runs before update

4. Identify the error in this React Native state update code:

const [items, setItems] = useState([]);
function addItem(newItem) {
  items.push(newItem);
  setItems(items);
}

medium

A. Directly mutating state array before setItems

B. Using useState with an array is invalid

C. Missing return statement in addItem

D. setItems should be called without arguments

Solution

1. Step 1: Check how state is updated

   The code mutates the existing array with push, which is not allowed because state must be immutable.

2. Step 2: Understand correct update method

   Instead, create a new array copy with the new item and pass it to setItems.

3. Final Answer:

   Directly mutating state array before setItems -> Option A

4. Quick Check:

   State must be immutable; don't mutate arrays [OK]

Hint: Never mutate state directly; always create new objects [OK]

Common Mistakes:

• Mutating arrays or objects directly
• Thinking useState can't hold arrays
• Calling setItems with no arguments

5. You have a React Native app with multiple screens needing to share user login status. Which state management approach is best?

hard

A. Use useState in each screen separately

B. Use inline styles to store login state

C. Use React Context API to share login state globally

D. Use local variables in each screen

Solution

1. Step 1: Identify need for shared state

   Login status must be accessible across multiple screens, so state must be shared globally.

2. Step 2: Choose appropriate state management

   React Context API allows sharing state across components without prop drilling, ideal for global data like login status.

3. Final Answer:

   Use React Context API to share login state globally -> Option C

4. Quick Check:

   Shared state across screens = Context API [OK]

Hint: Share global state with Context API, not local useState [OK]

Common Mistakes:

• Using separate useState in each screen causing inconsistent state
• Trying to store state in local variables
• Confusing styles with state