Empty State
What Is an Empty State in UI Design?
An empty state is a user interface shown when an application has no content, data, or results to display. It explains what is missing and helps users decide what to do next.
Types of Empty States and How They Differ
The message should match why no content appears. Loading and error screens are not true empty states because data may still arrive or a system issue needs resolution.
| State | User need | Message and action |
|---|---|---|
| First use | Learn how to begin | Explain the feature and offer “Create your first item.” |
| User-cleared | Confirm completion | Recognize the result and suggest an optional next task. |
| No results | Recover a search | Show the query and suggest changing terms. |
| Filtered-out | See hidden records | Name the active filter and offer “Clear filters.” |
| Permission-restricted | Understand access limits | Explain that access is required and direct users to request it. |
| Unavailable data | Know whether to wait or retry | Describe the source issue and provide a retry action. |
How an Empty State Should Guide the User
A useful empty state removes uncertainty. Design it around the cause, not a generic message.
- Identify why the view has no content, such as first use, filtering, or restricted access.
- State the reason in plain language.
- Offer one relevant action, such as creating an item or clearing filters.
- Keep filters, search terms, and navigation visible.
- Test it on small screens and alongside loading, error, and populated views.
Benefits of Well-Designed Empty States
Clear empty screens make an application easier to understand when it might otherwise feel broken.
- They explain why content is absent.
- They teach first-time users how a feature works.
- They help users recover from searches and filters.
- They turn an inactive screen into a productive next step.
Practical Limits and Common Empty State Mistakes
An illustration alone cannot explain a missing result. The interface needs accurate, actionable information.
- Avoid vague copy such as “Nothing here” when the cause is known.
- Do not present a network error as a normal empty state.
- Do not hide filters or search terms that caused an empty result.
- Do not offer actions the current user cannot complete.
- Do not rely on color alone to communicate status or access restrictions.
Empty State Examples for Apps and Dashboards
A new task list can say, “No tasks yet,” with a “Create task” button. An analytics dashboard can explain that data appears after an event is tracked. A no-results page should repeat the search term and suggest clearing filters. A filtered customer table should identify and let users remove the active filter.
Building Empty States with Emergent
When building an app with Emergent, specify first-use, no-results, permission, loading, and error behavior in the prompt. Its AI app builder can create connected interface states, while an AI dashboard builder can account for charts and tables before data exists. For consistent behavior, define transitions with a state machine. Build clearer app experiences with Emergent.
on Emergent today

