Navigation state persistence in React Native - Build, Publish & Deploy

Build & Publish - Navigation state persistence

Performance Impact

Persisting navigation state helps users return exactly where they left off, improving user experience. However, saving and restoring state can add slight overhead during app startup and navigation changes. If not optimized, it may cause frame drops below 60fps, especially on low-end devices. Memory usage increases slightly as navigation state data is stored in memory or local storage.

Optimization Techniques

To keep 60fps smoothness, save navigation state asynchronously using lightweight storage like AsyncStorage or secure storage. Debounce state saves to avoid frequent writes. Restore state quickly by loading only essential parts before rendering. Use React Native's useEffect hooks smartly to avoid blocking UI thread. Avoid saving large or unnecessary data in navigation state.

App Bundle Size and Startup Time

Navigation state persistence itself adds minimal bundle size since it relies on existing libraries like @react-navigation/native and @react-native-async-storage/async-storage. However, improper state management can increase startup time if large or complex states are restored synchronously. Keep saved state small and restore lazily to minimize startup delays.

iOS vs Android Differences

Both platforms support navigation state persistence similarly in React Native. iOS apps may have stricter background execution limits affecting when state can be saved. Android devices vary widely in memory and storage speed, so asynchronous saving is critical. iOS requires code signing and provisioning profiles but this does not affect navigation state persistence directly.

Store Review Guidelines

Ensure your app complies with Apple's Human Interface Guidelines by preserving user context naturally. Avoid unexpected navigation resets that confuse users. For Google Play, ensure your app does not misuse storage permissions when saving state. Both stores require apps to handle state restoration gracefully after crashes or updates.

Self-Check Question

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

• Navigation state restoration is blocking the main thread synchronously.
• Too much data is saved in navigation state causing slow deserialization.
• State saving is triggered too frequently, causing performance bottlenecks.

Key Result

Persist navigation state asynchronously and keep saved data minimal to ensure smooth 60fps UI and fast app startup while meeting store guidelines.

Practice

1. What is the main purpose of navigation state persistence in a React Native app?

easy

A. To change the app's theme based on user preference

B. To speed up the app's loading time by caching images

C. To save the user's current screen so they return to it after closing the app

D. To reset the app to the home screen every time it opens

Solution

1. Step 1: Understand navigation state persistence

   Navigation state persistence means saving where the user is in the app so they can continue from the same place later.

2. Step 2: Identify the correct purpose

   Only To save the user's current screen so they return to it after closing the app describes saving the current screen to restore it after app restart.

3. Final Answer:

   To save the user's current screen so they return to it after closing the app -> Option C

4. Quick Check:

   Navigation state persistence = save current screen [OK]

Hint: Remember: persistence means saving state for later use [OK]

Common Mistakes:

• Confusing navigation state with app theme or cache
• Thinking it resets app screens instead of saving them

2. Which of the following is the correct way to use NavigationContainer for state persistence?

easy

A.

B.

C.

D.

Solution

1. Step 1: Recall NavigationContainer props for persistence

   The correct props are initialState to set saved state and onStateChange to save new state.

2. Step 2: Match options with correct props

   Only uses initialState and onStateChange correctly.

3. Final Answer:

   <NavigationContainer initialState={savedState} onStateChange={saveState}> -> Option D

4. Quick Check:

   Use initialState and onStateChange props [OK]

Hint: Look for exact prop names: initialState and onStateChange [OK]

Common Mistakes:

• Using wrong prop names like state or onChange
• Swapping savedState and saveState variables

3. Given this code snippet, what will happen after the user navigates to 'Profile' and the app restarts?

const [initialState, setInitialState] = React.useState();
React.useEffect(() => {
  AsyncStorage.getItem('NAV_STATE').then(state => {
    if(state) setInitialState(JSON.parse(state));
  });
}, []);

 AsyncStorage.setItem('NAV_STATE', JSON.stringify(state))}
>
  {/* screens */}
;

medium

A. The app opens on the default initial screen ignoring saved state

B. The app opens on the 'Profile' screen automatically

C. The app crashes due to missing navigation state

D. The app opens on a blank screen

Solution

1. Step 1: Understand AsyncStorage usage

   The code loads saved navigation state from AsyncStorage and sets it as initialState.

2. Step 2: Effect of initialState on NavigationContainer

   Passing initialState restores the last screen, so the app opens on 'Profile' after restart.

3. Final Answer:

   The app opens on the 'Profile' screen automatically -> Option B

4. Quick Check:

   Saved state restores last screen [OK]

Hint: Saved state in initialState restores last screen [OK]

Common Mistakes:

• Assuming app ignores saved state and resets
• Thinking missing state causes crash

4. Identify the bug in this code that tries to persist navigation state:

const [navState, setNavState] = React.useState();

React.useEffect(() => {
  AsyncStorage.getItem('NAV_STATE').then(state => {
    setNavState(state);
  });
}, []);

 AsyncStorage.setItem('NAV_STATE', JSON.stringify(state))}
>
  {/* screens */}
;

medium

A. The saved state is not parsed from JSON before setting navState

B. The onStateChange callback should not stringify the state

C. initialState should be set to null instead of undefined

D. AsyncStorage.getItem should be called inside onStateChange

Solution

1. Step 1: Check AsyncStorage.getItem usage

   AsyncStorage.getItem returns a JSON string, so it must be parsed before use.

2. Step 2: Identify missing JSON.parse

   The code sets navState directly to the string, causing navigation to fail.

3. Final Answer:

   The saved state is not parsed from JSON before setting navState -> Option A

4. Quick Check:

   Parse JSON before setting state [OK]

Hint: Always parse JSON from AsyncStorage before using [OK]

Common Mistakes:

• Forgetting JSON.parse on saved state
• Misusing onStateChange callback

5. You want to persist navigation state but only save it after the user has navigated at least once. Which approach correctly implements this behavior?

hard

A. Use a ref to track if navigation happened, then save state in onStateChange only if true

B. Save state immediately on app start inside useEffect

C. Call AsyncStorage.clear() before saving state to avoid duplicates

D. Set initialState to null and never update it

Solution

1. Step 1: Understand conditional saving need

   We want to save navigation state only after user navigates once, so we track navigation occurrence.

2. Step 2: Use a ref to track navigation

   A ref can store a boolean flag that updates on first navigation, then onStateChange saves state only if true.

3. Step 3: Evaluate other options

   Save state immediately on app start inside useEffect saves immediately, ignoring condition; C clears storage unnecessarily; D disables persistence.

4. Final Answer:

   Use a ref to track if navigation happened, then save state in onStateChange only if true -> Option A

5. Quick Check:

   Track navigation with ref before saving state [OK]

Hint: Use a ref flag to save state only after first navigation [OK]

Common Mistakes:

• Saving state too early before navigation
• Clearing storage unnecessarily
• Ignoring initialState updates