Fallback UI patterns in React - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a fallback UI in React?

A fallback UI is a simple interface shown temporarily while the main content is loading or when an error occurs. It helps keep the app user-friendly by showing something instead of a blank screen.

beginner

How does React's <Suspense> component help with fallback UI?

<Suspense> lets you specify a fallback UI to show while waiting for some code or data to load. Once loading finishes, it shows the real content automatically.

intermediate

What is the purpose of an error boundary in fallback UI patterns?

An error boundary catches errors in child components and shows a fallback UI instead of crashing the whole app. This keeps the app stable and user-friendly.

beginner

Why is it important to keep fallback UIs simple and fast?

Fallback UIs should be simple and quick to show so users don’t wait long and don’t get confused. It improves the feeling of a smooth app experience.

beginner

Name two common fallback UI patterns in React.

1. Using <Suspense> with a loading spinner or message. 2. Using error boundaries to show an error message or alternative UI when something breaks.

What does React's <Suspense> component do?

A Manages global app state

B Shows a fallback UI while waiting for code or data to load

C Catches JavaScript errors in components

D Handles user input events

is designed to show fallback content while waiting for lazy-loaded components or data.

What is the main role of an error boundary?

A To style components

B To load components lazily

C To show a fallback UI when a child component throws an error

D To manage API calls

Error boundaries catch errors in their child components and display fallback UI instead of crashing.

Which of these is NOT a good practice for fallback UIs?

A Provide clear feedback to users

B Keep them simple and fast

C Use a spinner or loading message

D Show detailed app content immediately

Fallback UIs should be simple placeholders, not full app content, to keep loading fast and clear.

When should you use fallback UI patterns?

A While waiting for data or code to load, or when errors happen

B Only when styling components

C To handle user authentication

D To optimize images

Fallback UIs help during loading or error states to improve user experience.

Which React feature helps you show fallback UI during lazy loading?

A <Suspense>

B <ErrorBoundary>

C <useState>

D <useEffect>

is the React component designed for fallback UI during lazy loading.

Explain how fallback UI patterns improve user experience in React apps.

Think about what users see when data or code is not ready yet.

Describe how you would implement a fallback UI using React's Suspense and error boundaries.

Combine two React features to handle loading and errors.

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