Why global state avoids prop drilling in React Native - Publishing Best Practices

Build & Publish - Why global state avoids prop drilling

Performance Impact

Using global state in React Native helps avoid passing props through many layers of components, called prop drilling. This reduces unnecessary re-renders of intermediate components that do not use the data, improving frame rate and responsiveness. It also lowers memory use by preventing extra copies of data in props. Overall, global state can help maintain smooth 60fps animations and reduce battery drain by minimizing wasted updates.

Optimization Tips

To keep your app running smoothly at 60fps when using global state, use selectors or memoization to only update components that need changed data. Avoid putting large objects or functions directly in global state. Use libraries like Redux or React Context efficiently by splitting state into smaller slices. This reduces the work React does on each update and keeps UI fast and responsive.

App Size and Startup Time

Adding global state management libraries can increase your app bundle size slightly, usually by a few hundred kilobytes. However, this is often offset by cleaner code and easier maintenance. Startup time impact is minimal if you load state lazily or asynchronously. Avoid bundling large unused state logic to keep startup fast.

iOS vs Android Differences

Global state management works similarly on iOS and Android in React Native. Both platforms benefit from reduced prop drilling and improved performance. However, Android devices vary more in hardware, so optimization is more critical there to maintain smooth UI. iOS apps may have stricter memory limits, so efficient state updates help avoid app termination.

Store Review Guidelines

Neither Apple App Store nor Google Play Store has specific rules about using global state. However, both stores require apps to be stable and responsive. Efficient state management helps meet these requirements by preventing crashes and slow UI. Also, avoid exposing sensitive data in global state to comply with privacy guidelines.

Self-Check Question

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

• You might be passing too many props through many components, causing slow rendering.
• Or your global state updates are causing unnecessary re-renders of large parts of the UI.
• Check if you can use global state with memoization or selectors to reduce updates.

Key Result

Using global state in React Native avoids prop drilling, improving app performance by reducing unnecessary re-renders and memory use, while slightly increasing bundle size. Proper optimization ensures smooth 60fps UI on both iOS and Android and helps meet app store stability guidelines.

Practice

1. Why is using global state preferred over prop drilling in React Native apps?

easy

A. Because global state requires more code to pass data

B. Because prop drilling improves performance by passing props deeply

C. Because prop drilling avoids using any state management

D. Because global state allows direct data sharing without passing props through many components

Solution

1. Step 1: Understand prop drilling

   Prop drilling means passing data through many layers of components even if intermediate ones don't need it.

2. Step 2: Understand global state benefits

   Global state shares data directly with any component that needs it, avoiding unnecessary prop passing.

3. Final Answer:

   Because global state allows direct data sharing without passing props through many components -> Option D

4. Quick Check:

   Global state avoids prop drilling = C [OK]

Hint: Global state shares data directly, skipping intermediate props [OK]

Common Mistakes:

• Thinking prop drilling improves performance
• Believing global state requires more code
• Confusing prop drilling with avoiding state

2. Which of the following is the correct way to access global state using React Context in React Native?

easy

A. const value = useReducer(MyContext);

B. const value = useState(MyContext);

C. const value = useContext(MyContext);

D. const value = useEffect(MyContext);

Solution

1. Step 1: Recall React Context usage

   To access global state via React Context, useContext hook is used with the context object.

2. Step 2: Identify correct hook

   useState manages local state, useEffect manages side effects, useReducer manages complex state logic, but none access context directly.

3. Final Answer:

   const value = useContext(MyContext); -> Option C

4. Quick Check:

   Access context with useContext = D [OK]

Hint: Use useContext to read global state from context [OK]

Common Mistakes:

• Using useState instead of useContext for context
• Confusing useEffect with state access
• Trying to use useReducer directly for context

3. Given this React Native code snippet using global state, what will be the output when the button is pressed?

const CountContext = React.createContext(0);

function Display() {
  const count = React.useContext(CountContext);
  return {count};
}

function App() {
  const [count, setCount] = React.useState(0);
  return (
    
      
       setCount(count + 1)} />
    
  );
}

medium

A. The displayed number stays 0 always

B. The displayed number increases by 1 each button press

C. The app crashes due to missing context

D. The button does not respond to presses

Solution

1. Step 1: Understand context and state connection

   The count state is provided via CountContext.Provider and updated on button press.

2. Step 2: Trace button press effect

   Pressing the button calls setCount(count + 1), updating count and re-rendering Display with new value.

3. Final Answer:

   The displayed number increases by 1 each button press -> Option B

4. Quick Check:

   Context updates with state changes = B [OK]

Hint: State update triggers context value change and re-render [OK]

Common Mistakes:

• Assuming context value never changes
• Thinking button does not update state
• Believing app crashes without provider

4. Identify the bug in this React Native code that tries to use global state but still requires prop drilling:

const UserContext = React.createContext();

function Profile({ user }) {
  return {user.name};
}

function App() {
  const user = { name: 'Anna' };
  return (
    
      
    
  );
}

medium

A. Profile component should use useContext(UserContext) instead of props

B. UserContext.Provider is missing a value prop

C. User object is not defined

D. Profile component should be a class component

Solution

1. Step 1: Check how Profile receives data

   Profile expects a user prop but is rendered without props, causing undefined user.

2. Step 2: Use context to avoid prop drilling

   Profile should use useContext(UserContext) to get user directly from global state.

3. Final Answer:

   Profile component should use useContext(UserContext) instead of props -> Option A

4. Quick Check:

   Use context hook to avoid prop drilling = A [OK]

Hint: Use useContext inside components to get global state [OK]

Common Mistakes:

• Forgetting to use useContext in child components
• Assuming Provider needs no value prop
• Thinking class components are required

5. You have a React Native app with deeply nested components needing the same user data. Which approach best avoids prop drilling and keeps code clean?

hard

A. Use React Context to create a global user state and access it with useContext in any component

B. Pass user data as props through every nested component manually

C. Store user data in local component state of the top-level component only

D. Use multiple useState hooks in each nested component to hold user data

Solution

1. Step 1: Understand prop drilling problem

   Passing props through many nested components is tedious and error-prone.

2. Step 2: Use global state with React Context

   React Context allows sharing user data globally, so any component can access it directly without prop passing.

3. Final Answer:

   Use React Context to create a global user state and access it with useContext in any component -> Option A

4. Quick Check:

   Global state with context avoids prop drilling = A [OK]

Hint: React Context shares data globally, no prop passing needed [OK]

Common Mistakes:

• Passing props through every nested component
• Using local state only at top level
• Duplicating state in nested components