VANKPA
Start a project

Web applications

Make empty app screens explain what comes next.

Distinguish a first-use screen, no matching results, and unavailable data so users do not have to guess.

Illustrated scene: A woman studies an empty app screen at a sunlit desk.

An empty screen can mean several things: no records exist, a filter removed every result, access is limited, or the data failed to load. A message such as “Nothing here” leaves the user to decide which explanation applies. The app should make that state understandable.

Identify the reason for the empty view

For a new workspace, explain the first useful action and what will appear afterward. For a search with no matches, show the current query and offer a way to adjust it. For a loading failure, give a recovery path without suggesting that the records were deleted.

Avoid revealing restricted record details through an empty-state explanation. A permission boundary should be clear without confirming private information the user is not authorized to know.

Offer one relevant action

Imagine a hypothetical client portal with no uploaded documents. A new client may need to upload a file, while a returning client may be viewing the wrong project. Those situations call for different instructions. A generic “Get started” button cannot serve both reliably.

Keep examples clearly labeled as samples and avoid populating the workspace with realistic-looking records that could be mistaken for customer data. If a sample is interactive, make its limits obvious.

Test the transitions

Check what happens after the first record is created, after filters are cleared, and after a failed request succeeds. The empty state should disappear at the right moment and preserve any work the user already entered.

Review support questions about missing information. They can reveal that an empty screen is being interpreted as lost data, even when the underlying records are intact.

Start with the screen a new user sees first. Ask them to explain why it is empty and what they would do next. A useful empty state makes the next action clear while accurately describing what the application knows.

Plan your next step.

Explore the related serviceDiscuss your project
Help me choose