QuizzesDesigning the Loading, Error and Empty States — Concept Check
intermediate
react

Designing the Loading, Error and Empty States — Concept Check

Questions on Designing the Loading, Error and Empty States. The states around the data are most of the perceived quality of an app. They are also where juniors are most visibly junior in a code review.

8 minutes 8 questions Pass at 70%
Time Limit
8 minutes - timer starts when you begin
Change Answers Freely
Revisit and change any answer before submitting
Full Review After Submit
Correct answers and explanations shown for every question
Auto-submit on timeout
Quiz submits automatically when time runs out

Questions in this quiz

8 questions on Designing the Loading, Error and Empty States — Concept Check. Work through them here, then start the quiz to answer them and see your score.

  1. 1.While implementing a loading state, a developer uses a spinner in the middle of an empty page. What is a better approach?

    • AAdd more spinners to indicate loading speed.
    • BUse a skeleton to match the shape of incoming data.
    • CKeep the spinner as it is more visually appealing.
    • DUse a loading bar at the bottom of the page.
  2. 2.A developer notices that a page flashes briefly when loading data. What could be a reason for this?

    • AThe network connection is unstable.
    • BThe skeleton is shown for too short a duration.
    • CThe data is too large to load efficiently.
    • DThe spinner is not centered properly.
  3. 3.When handling errors, why is it important to distinguish between different error statuses?

    • ATo provide specific guidance to the user on what to do next.
    • BTo avoid showing any error messages to the user.
    • CTo make the error messages longer and more detailed.
    • DTo ensure the application looks more professional.
  4. 4.A user sees 'No submissions yet' on their dashboard. What does this empty state indicate?

    • AThe filter applied has no matching results.
    • BThe user has completed all available tasks.
    • CThe user has not made any submissions yet.
    • DThe application is offline.
  5. 5.A developer uses a raw stack trace in the error message. Why is this problematic?

    • AIt makes the application faster.
    • BIt helps users debug their own issues.
    • CIt provides too much useful information.
    • DIt exposes internal details to the user.
  6. 6.What is a common mistake when designing an empty state for a completed queue?

    • AUsing a generic message instead of a positive tone.
    • BOffering to clear filters that don't exist.
    • CMaking the message too encouraging.
    • DShowing a loading spinner instead.
  7. 7.Why should a loading skeleton not be shown for responses under 80ms?

    • AIt is too resource-intensive.
    • BIt distracts from the main content.
    • CIt makes the application look slower.
    • DIt appears as a glitch, confusing the user.
  8. 8.What should a developer do if the application detects the user is offline?

    • AShow a message indicating offline status.
    • BShow a generic error message.
    • CContinue attempting to load data.
    • DRetry the request immediately.