Three kinds of empty
| Type | Cause | What to show |
|---|---|---|
| First use | Nothing created yet | What this area is for and a button to create the first item |
| No results | A search or filter matches nothing | Say so, show the active filters, and offer to clear them |
| Cleared | The user completed or removed everything | A short acknowledgment, and optionally what to do next |
| Error | Loading failed | What went wrong and a way to retry |
Treating them all the same, with a blank panel or a vague "No data", is a common source of confusion.
What NN/g recommends
NN/g's guidance on empty states in complex applications points to three themes: communicate system status, offer learning cues, and provide direct pathways to key tasks. A blank container does none of these. It also risks the user thinking the app is broken.
They also warn against messages that change a moment later. A "No records" note that is replaced a second later by a list makes people distrust the interface. Show a loading state until you know the answer.
A pattern that works
An effective empty state
Write it in your users' words
Skip "No items found". Try "No invoices yet. Create your first invoice to get paid." Specific, short, and helpful. Test the copy with a few new users to see if they know what to do next.



