Loading and error states in React Native - Build, Publish & Deploy

Build & Publish - Loading and error states

Performance Impact

Loading and error states help manage user expectations during data fetching or processing. Properly implemented, they prevent unnecessary re-renders and reduce CPU usage by avoiding repeated failed requests. However, excessive or complex animations in loading indicators can reduce frame rates below the smooth 60fps target, causing janky UI. Memory impact is minimal if states are simple, but large error images or heavy animations can increase memory use and battery drain.

Optimization Tips

• Use lightweight, simple loading indicators like spinners or skeleton placeholders instead of heavy animations.
• Cache data to avoid repeated loading states on the same content.
• Debounce or throttle network requests to prevent multiple simultaneous loads.
• Use React Native's useMemo or React.memo to avoid unnecessary re-renders of loading/error components.
• Show error messages only when necessary and keep UI minimal to maintain 60fps.

App Size and Startup Time

Loading and error states themselves add negligible size to the app bundle if implemented with native components and simple styles. Avoid importing large third-party animation libraries just for loading indicators, as they can increase bundle size significantly and slow startup time. Using built-in React Native components and minimal assets keeps the app lightweight and fast to launch.

iOS vs Android Differences

Both platforms support similar loading and error UI patterns, but native components differ slightly. iOS uses ActivityIndicator with a default spinner style, while Android's spinner may look different. Error messages should follow platform conventions: iOS favors subtle alerts, Android uses snackbars or toasts. Also, Android devices vary more in performance, so keep loading states lightweight to maintain smooth UI across devices.

Store Review Guidelines

• Apple App Store requires apps to handle loading and error states gracefully to avoid crashes or frozen screens (Apple Human Interface Guidelines).
• Google Play expects apps to provide clear feedback during loading and errors to prevent user confusion (Material Design guidelines).
• Both stores reject apps that appear unresponsive or crash due to unhandled errors.
• Ensure error messages do not expose sensitive information or internal error codes.

Self-Check Question

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

• Network requests are not optimized or retried properly, causing delays.
• Loading indicators use heavy animations slowing down rendering.
• Data fetching is blocking the main thread, freezing UI.
• Error states are not handled, causing repeated failed loads.

Key Result

Efficient loading and error states improve user experience by maintaining smooth 60fps UI and preventing app freezes. Use simple indicators and handle errors gracefully to meet store guidelines and optimize app size and performance.

Practice

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

easy

A. To display an error message when something goes wrong

B. To show the user that data is being fetched or processed

C. To permanently hide content from the user

D. To restart the app automatically

Solution

1. Step 1: Understand loading state role

   Loading states inform users that the app is busy fetching or processing data.

2. Step 2: Differentiate from error state

   Error states show problems, not loading progress.

3. Final Answer:

   To show the user that data is being fetched or processed -> Option B

4. Quick Check:

   Loading state = show progress [OK]

Hint: Loading means waiting for data, not errors [OK]

Common Mistakes:

• Confusing loading with error states
• Thinking loading hides content permanently
• Assuming loading restarts the app

2. Which of the following is the correct way to declare a loading state using React Native's useState hook?

easy

A. const loading = useState(false);

B. let loading = useState(true);

C. var loading = useState(false);

D. const [loading, setLoading] = useState(false);

Solution

1. Step 1: Recall useState syntax

   useState returns an array with current value and setter function, usually destructured.

2. Step 2: Check options for correct destructuring

   const [loading, setLoading] = useState(false); correctly uses array destructuring with const and initial value false.

3. Final Answer:

   const [loading, setLoading] = useState(false); -> Option D

4. Quick Check:

   useState destructuring = const [loading, setLoading] = useState(false); [OK]

Hint: useState returns [value, setter], destructure with const [a,b] [OK]

Common Mistakes:

• Not destructuring the array from useState
• Using let or var instead of const
• Assigning useState directly to a variable without destructuring

3. Given this React Native snippet, what will be displayed when loading is true?

const [loading, setLoading] = useState(true);
return (
  loading ? Loading... : Data loaded
);

medium

A. Loading...

B. Nothing is displayed

C. Data loaded

D. Error message

Solution

1. Step 1: Check the value of loading

   loading is true initially.

2. Step 2: Evaluate the ternary expression

   If loading is true, Loading... is returned and shown.

3. Final Answer:

   Loading... -> Option A

4. Quick Check:

   loading true shows loading text [OK]

Hint: Ternary shows first option if condition true [OK]

Common Mistakes:

• Confusing true and false branches
• Thinking nothing shows when loading is true
• Assuming error message shows automatically

4. Identify the error in this React Native code handling loading and error states:

const [loading, setLoading] = useState(false);
const [error, setError] = useState(null);

if (loading) {
  return Loading...;
} else if (error) {
  return Error occurred;
}
return Data loaded;

medium

A. Error state should be a boolean, not null

B. The if-else logic is reversed

C. Loading state should be true initially to show loading

D. No error, code works fine

Solution

1. Step 1: Check initial loading state

   Loading is false initially, so loading screen never shows on start.

2. Step 2: Understand typical loading flow

   Loading should start as true while fetching data, then false after.

3. Final Answer:

   Loading state should be true initially to show loading -> Option C

4. Quick Check:

   Initial loading true needed to show loading [OK]

Hint: Loading usually starts true before data fetch [OK]

Common Mistakes:

• Setting loading false initially hides loading screen
• Thinking error must be boolean
• Assuming if-else order is wrong

5. You want to show a loading spinner while fetching data, then show an error message if fetch fails, or the data if successful. Which React Native pattern correctly handles these states?

hard

A. Use separate states: loading (boolean), error (string|null), data (object|null), and conditionally render based on these

B. Only use a loading state and ignore errors

C. Use a single state variable for all three states with strings 'loading', 'error', 'data'

D. Render data immediately without any loading or error checks

Solution

1. Step 1: Understand state separation

   Separate states for loading, error, and data allow clear control of UI for each condition.

2. Step 2: Evaluate options

   Use separate states: loading (boolean), error (string|null), data (object|null), and conditionally render based on these uses best practice: boolean loading, error message or null, and data object or null.

3. Final Answer:

   Use separate states: loading (boolean), error (string|null), data (object|null), and conditionally render based on these -> Option A

4. Quick Check:

   Separate states for clarity and control [OK]

Hint: Use separate states for loading, error, and data [OK]

Common Mistakes:

• Ignoring error handling
• Using one string state for all conditions
• Rendering data without waiting for fetch