Designing for the empty state

The first screen a new user sees is usually empty. Why we treat empty states as a first impression, not an afterthought.

Design

Design

The empty screen is the first screen

Every user starts with nothing, design for that moment.

An empty state is a chance to orient, teach and invite the first action, so instead of a blank void, new users get a clear, encouraging path to their first win.

What a good empty state does

Explains the space

Says plainly what will live here once it's set up.

Offers one action

A single, obvious first step to fill it.

Sets the tone

A first impression that feels intentional, not broken.

First impressions

The empty screen is a welcome, not a dead end

Every new user starts with nothing on the page.

The very first thing someone sees in a new tool is usually blank, no data, no history, nothing to react to. Treated as an afterthought, that moment feels broken; treated with care, it becomes the clearest onboarding you have.

A good empty state explains what goes here, why it matters, and offers the single next action that gets the user moving, turning a void into a nudge.

Highlights

What a good empty state does

Orients

Explains what this screen is for.

Teaches

Shows the first useful action.

Invites

Makes starting feel easy.

A closer look

The empty state is your best onboarding surface

An empty screen is the one moment you have the user's full attention and zero competing content, wasting it on a grey illustration and 'No items yet' is a missed conversation. The empty state should answer three things: what belongs here, why it's valuable, and the one action that starts.

The best pattern is a worked example: a sample project, a demo record, a pre-filled template the user can poke at and then replace. Showing a filled state teaches the product faster than describing it ever will.

Remember that emptiness has flavors, brand new, filtered-to-nothing, permission-denied and everything-done each deserve different words. 'No results' when a filter is too narrow is a dead end; 'No results, try clearing the date filter' is a path.

Team for AppsProduct & Engineering

We build software for teams who want their tools to fit the way they actually work — web, mobile, AI and the systems that tie them together. We write here about what we learn shipping it.

Have a project in mind?

Tell us what you're building and we'll get back to you within one business day.