The quiet luxury of a good empty state
- Design
- Product
An empty state is the first honest conversation a product has with someone. There’s no data to hide behind, no clever chart, no list of things you’ve already done. Just a blank space and a question: what now?
Most teams treat that moment as a formality. A grey illustration, a line of copy written at the last minute, a button that says “Get started.” And then everyone moves on to the screens that feel more important.
Nothing is still something
Think about the last time you opened an app and found it empty. You probably felt one of two things: curiosity or suspicion. Curiosity when the empty state told you exactly what to do next. Suspicion when it looked like something had failed to load.
That difference is rarely about the artwork. It’s about whether the page understands why you’re there. An empty inbox says “you’re all caught up.” An empty project board says “add your first task.” Both are empty. Only one of them is comforting.
The best empty states I’ve used do three small things:
- They name the situation without apologising for it.
- They offer one clear next step, not four.
- They leave a little room to breathe.
Design the absence
It helps to treat emptiness as a feature rather than a bug. If you were designing a blank sheet of paper, you’d think about margins and weight and where the first mark should go. The same applies here.
A few questions worth asking while the screen is still empty:
- What did this person just try to do?
- What would make them feel smart rather than stuck?
- What can we remove so the next action is obvious?
The answers usually point to something quieter than the first draft. Fewer illustrations. Smaller type. A single sentence that sounds like a person wrote it.
There’s a particular pleasure in a product that feels calm when there’s nothing in it. It suggests that when there is something, it will be handled just as carefully.