Design an empty state that explains what happens next

An empty state should explain why there is no content and what the person can do next. First use, no search results, and unavailable access are different situations. Give each the right explanation rather than reusing “Nothing here yet” everywhere.

Identify the actual state

Do not call a network failure an empty result. If you cannot retrieve the data, say that and provide a recovery action. Otherwise the person may believe their work disappeared.

A fictional search state

No guides match “invoice astrology.”
Try a shorter term, or clear the search to see all free guides.
[Clear search]

This message uses the actual query and a working reset action. An illustration can add personality, but it should not replace the explanation or push the control off a small screen.

Keep the first-use state useful

Show one representative example or a clear action when appropriate. Avoid filling the screen with fake customer content that looks like the person’s own records. If sample data is displayed, label it as sample data and make removal or replacement obvious.

Review these empty states.
Identify whether each represents first use, no matches, missing access,
or a failed request.
Write a short explanation and one appropriate recovery action.
Do not invent content or promise a recovery the app cannot perform.
States and actual behavior: [paste]

Test recovery

Clear the search, reset the filter, retry the request, or follow the access path. The message is only useful if the promised action works. Check that status changes are understandable to keyboard and assistive-technology users.

An empty state can be welcoming without being cute. The person usually needs to understand whether the situation is expected, whether their data is intact, and which action is worth taking next.