# An empty dashboard owes the user an explanation

No results can mean no matches, missing coverage, stale data or a failed request. Give each state its own sentence.

By AppRill Editorial · Published 2026-09-08
Canonical: https://apprill.app/blog/empty-states-real-data

“Nothing here yet” is doing far too much work in many apps.

It can mean the user has not added anything, the search found no matches, a data source has never run, or the request failed. Those situations require different next steps.

## Name what you know

For a hypothetical app-intelligence page, no observed ads should not become “this app does not advertise.” It may mean no ads were found in the covered sources and period. If coverage is unavailable, say that plainly.

A useful empty state contains the result, its scope and one relevant action. “No reviews collected for this storefront yet” can link to the store or explain when collection happens. It should not invite a customer to retry an internal admin job.

## Keep failures distinct

A failed request should not silently render as an empty collection. Otherwise the interface teaches users to draw conclusions from outages.

Preserve already loaded data when reasonable, mark its age and offer a retry. Avoid exposing raw stack traces, provider tokens or internal operational language in the customer experience.

## Use examples carefully

A demo can help explain a feature, but label it as a demo and keep it visually distinct from live evidence. Do not populate a blank revenue chart with plausible-looking values to make the screen feel finished.

Test the page with no records, one record, stale records, a partial response and a complete failure. These states are ordinary product behavior, not obscure edge cases.

The right empty state can increase trust because it explains the boundary of the product's knowledge. The wrong one can turn missing data into a confident false conclusion.

When the dashboard has nothing to show, it still has something important to say: why, what that means and what the user can usefully do next.


## Sources