The decision that matters
Avoid using one cheerful “Nothing here yet” message for every condition. A new workspace can invite creation, while an empty search should offer a way to adjust or clear the query. An access restriction should not encourage someone to create records they cannot manage. A failed request needs a retry path and a visible error, not an empty list that implies the data disappeared.
A practical scenario
In a document library, a new owner might see “Create your first document” with a clear action. A member searching for an absent term should see the query and a reset option. During loading, the application should not briefly announce that there are zero documents. Each state reflects a different next step.
Before you ship
- Separate loading, empty, filtered and failed states.
- Match the action to the user’s permissions.
- Keep context such as the active filter visible.
A useful next step
Review each list screen with no records, no matching records and an interrupted request. These cases are easy to miss when testing with a populated administrator account. Good empty states make the product understandable before it is busy.
Primary reference & further reading
This guide combines general engineering recommendations with an illustrative scenario. Provider behavior can change; check current documentation before applying it. Read our editorial approach.