Fallback UI patterns in React

Introduction

Fallback UI patterns show a simple message or design when the main content is loading or has an error. This helps users understand what is happening instead of seeing a blank screen.

When loading data from the internet and you want to show a loading spinner or message.

When a part of your app crashes and you want to show a friendly error message.

When waiting for a slow component to load and you want to keep the user informed.

When you want to improve user experience by avoiding empty or broken screens.

Syntax

React

function Component({ loading, error }) {
  if (loading) {
    return <FallbackUI />;
  }
  if (error) {
    return <ErrorUI />;
  }
  return <MainContent />;
}

Use simple conditional checks to decide which UI to show.

Fallback UI can be a spinner, message, or any React element.

Examples

Shows a loading message while waiting.

React

function Loading() {
  return <p>Loading...</p>;
}

function MyComponent({ loading }) {
  if (loading) {
    return <Loading />;
  }
  return <p>Data loaded!</p>;
}

Shows an error message if there is a problem.

React

function ErrorFallback() {
  return <p>Oops! Something went wrong.</p>;
}

function MyComponent({ error }) {
  if (error) {
    return <ErrorFallback />;
  }
  return <p>All good!</p>;
}

Combines loading and error fallback UIs.

React

function MyComponent({ loading, error }) {
  if (loading) return <p>Loading...</p>;
  if (error) return <p>Error occurred.</p>;
  return <p>Content is ready.</p>;
}

Sample Program

This React component shows a loading message first. After 1.5 seconds, it either shows data or an error message. It uses fallback UI patterns to keep the user informed.

React

import React, { useState, useEffect } from 'react';

function Loading() {
  return <p aria-live="polite">Loading data, please wait...</p>;
}

function ErrorFallback() {
  return <p role="alert">Error loading data. Try again later.</p>;
}

function DataDisplay({ data }) {
  return <div>
    <h2>Data Loaded</h2>
    <pre>{JSON.stringify(data, null, 2)}</pre>
  </div>;
}

export default function App() {
  const [data, setData] = useState(null);
  const [loading, setLoading] = useState(true);
  const [error, setError] = useState(false);

  useEffect(() => {
    setTimeout(() => {
      // Simulate fetch success or failure
      const success = true;
      if (success) {
        setData({ message: 'Hello from server!' });
        setLoading(false);
      } else {
        setError(true);
        setLoading(false);
      }
    }, 1500);
  }, []);

  if (loading) return <Loading />;
  if (error) return <ErrorFallback />;
  return <DataDisplay data={data} />;
}

Important Notes

Always provide accessible roles and aria-live for fallback messages to help screen reader users.

Keep fallback UI simple and clear to avoid confusing users.

Test fallback UI by simulating slow network or errors in your app.

Summary

Fallback UI patterns improve user experience during loading or errors.

Use simple conditional rendering to show fallback content.

Make fallback UI accessible and easy to understand.

Practice

1. What is the main purpose of a fallback UI in React applications?

easy

A. To speed up the rendering of all components

B. To permanently replace the main UI with a different design

C. To disable user interactions during loading

D. To show a temporary interface while content is loading or an error occurs

Solution

1. Step 1: Understand fallback UI role

   Fallback UI is used to improve user experience by showing temporary content during loading or errors.

2. Step 2: Differentiate from permanent UI changes

   Fallback UI is temporary, not a permanent replacement or disabling interaction.

3. Final Answer:

   To show a temporary interface while content is loading or an error occurs -> Option D

4. Quick Check:

   Fallback UI = temporary loading/error display [OK]

Hint: Fallback UI shows temporary content during loading/errors [OK]

Common Mistakes:

• Thinking fallback UI is permanent
• Confusing fallback UI with performance optimization
• Assuming fallback UI disables all user actions

2. Which of the following is the correct way to render a fallback UI in React using conditional rendering?

easy

A. {isLoading ? <LoadingSpinner /> : <Content />}

B. {isLoading && <Content />}

C. {isLoading || <LoadingSpinner />}

D. {isLoading = <LoadingSpinner />}

Solution

1. Step 1: Review conditional rendering syntax

   Using the ternary operator ? : correctly chooses between fallback and main UI.

2. Step 2: Check each option's logic

   {isLoading ? <LoadingSpinner /> : <Content />} uses ternary correctly; B and C misuse logical operators; D uses assignment instead of comparison.

3. Final Answer:

   {isLoading ? <LoadingSpinner /> : <Content />} -> Option A

4. Quick Check:

   Ternary operator for fallback UI = {isLoading ? <LoadingSpinner /> : <Content />} [OK]

Hint: Use ternary operator for fallback UI rendering [OK]

Common Mistakes:

• Using && or || incorrectly for fallback UI
• Using assignment (=) instead of comparison
• Not providing both fallback and main UI in conditional

3. Given the code below, what will be rendered when hasError is true?

function MyComponent({ hasError, isLoading }) {
  if (hasError) {
    return <div>Error occurred</div>
  }
  if (isLoading) {
    return <div>Loading...</div>
  }
  return <div>Content loaded</div>
}

medium

A. Loading...

B. Error occurred

C. Content loaded

D. Nothing will render

Solution

1. Step 1: Check error condition first

   The component returns the error message immediately if hasError is true.

2. Step 2: Understand conditional order

   Since error check comes before loading, loading state is ignored if error exists.

3. Final Answer:

   <div>Error occurred</div> -> Option B

4. Quick Check:

   Error condition renders error UI first [OK]

Hint: Error check before loading shows error UI first [OK]

Common Mistakes:

• Assuming loading shows even if error is true
• Ignoring order of conditions
• Thinking content loads despite error

4. Identify the error in this fallback UI pattern code:

function Profile({ user }) {
  return (
    <div>
      {user ? <ProfileDetails user={user} /> : <LoadingSpinner />}
      {!user && <LoadingSpinner />}
    </div>
  )
}

medium

A. The conditional rendering syntax is invalid

B. The component will crash because user is undefined

C. The fallback UI <LoadingSpinner /> is shown twice when user is null

D. The fallback UI is missing for loading state

Solution

1. Step 1: Analyze conditional rendering logic

   The first condition shows LoadingSpinner if user is falsy.

2. Step 2: Check second condition

   The second condition shows LoadingSpinner if user is falsy, causing it to appear twice when user is falsy.

3. Final Answer:

   The fallback UI <LoadingSpinner /> is shown twice when user is null -> Option C

4. Quick Check:

   Duplicate fallback UI rendering due to conflicting conditions [OK]

Hint: Check if fallback UI appears more than once [OK]

Common Mistakes:

• Assuming fallback UI shows only once
• Confusing truthy and falsy conditions
• Ignoring duplicated components in render

5. You want to create a fallback UI that shows a spinner while data loads, an error message if loading fails, and the content once loaded. Which React pattern best handles this cleanly and accessibly?

hard

A. Use separate components for Loading, Error, and Content, and conditionally render them in order

B. Use nested ternary operators inside JSX to handle loading, error, and content states

C. Render all three components simultaneously and hide/show with CSS

D. Use a single state variable with string values and switch-case inside JSX

Solution

1. Step 1: Evaluate clarity and accessibility

   Separate components for each state improve readability and accessibility.

2. Step 2: Compare with other options

   Nested ternaries (B) reduce readability; rendering all simultaneously (C) wastes resources; switch-case in JSX (D) is less common and can be confusing.

3. Final Answer:

   Use separate components for Loading, Error, and Content, and conditionally render them in order -> Option A

4. Quick Check:

   Separate components for fallback states = Use separate components for Loading, Error, and Content, and conditionally render them in order [OK]

Hint: Separate components for each state improve clarity [OK]

Common Mistakes:

• Using nested ternaries that are hard to read
• Rendering all states at once and hiding with CSS
• Using complex switch-case inside JSX