0
Challenge · 53Routing & Data

Empty States

Coreused in ~70% of apps

A request can succeed and still return zero rows. If your UI only handles loading, error, and a non-empty list, that fourth case renders nothing — and a blank screen reads as broken, not as “you have no tasks yet.”

Core idea. An empty result is its own UI state, separate from loading and error: when the data is an empty array, render a designed screen — a shape, one sentence, and one call-to-action — that explains why it's empty and what to do next.
Playground, this isn't a screenshot
current stateEMPTY
··
<TaskList />items.length = 0
No tasks yet
Create your first task to get the board moving.
empty because…

Same list, three states. Loading shows skeletons, has-data shows rows, and emptyearns its own designed screen — art, one sentence, one CTA — tuned to whyit's empty. Flip the bug to feel how a blank box destroys that signal.

↑ play a little first, then dig in