Empty State
Design Processes
What a screen shows when there is nothing in it yet.
In practice
An empty state is the first thing a new user sees in a list, inbox, dashboard or project with no content — and it is usually neglected. A good one explains what will live here, shows how to add the first item, and sets a tone; a blank one leaves people wondering if something is broken. It is a small screen with an outsized effect on whether someone continues.
Questions
What is Empty State?
An empty state is the designed condition of an interface when it has no data to display, whether because the user is new, has cleared it, or a search returned nothing.
Why do you use Empty State?
It is the moment of maximum uncertainty for a new user. Filling it with guidance turns 'is this working?' into 'oh, I do this'.
How do you use/apply Empty State?
Say what the space is for, give one clear action to populate it, keep the tone human, and design distinct versions for first-use, cleared and no-results.
When do you use Empty State?
For every collection, list and dashboard — designed alongside the populated state, not after.
Who uses Empty State?
Product and UX designers.
