What is an empty state?
An empty state is what a screen displays before it has any content — the dashboard before the first project, the inbox before the first message, the report page before the first data. For new users it is not an edge case; it is the product's first impression, and most first sessions are decided on one.
Why it matters more than teams think
Designers and engineers see populated screens all day — their accounts are full. New users see the empty version of everything, and an empty screen with no guidance silently asks them to figure out the product's core loop unaided. The gap between "welcome aboard!" and "now what?" is where week-one churn is manufactured, and the empty state is that gap's address.
The three grades of empty state
- Blank — a void, maybe an icon. Actively harmful; reads as broken or bare.
- Explanatory — "projects will appear here." Honest but inert; describes the absence instead of ending it.
- Actionable — a single clear starting action ("Create your first project"), a template to start from, or sample data to react to. This is the only grade that converts.
Empty states and guided onboarding
The best pattern joins the two: the empty state carries the primary action, and a guided flow walks the user through performing it — a tour anchored to that very button, or a "show me how" trigger in the empty state itself. Fixing empty states is also the honest first answer to "do we need onboarding?": guidance layered over a blank void explains; an actionable empty state converts.
See the concepts running live.
Wakeline puts the whole vocabulary to work — tours, checklists, targeting, funnels — no-code on your app, free for 1,000 monthly active users.