6 minute read · Updated 2026-09-05
Why the happy path is only one state of a production interface, and what every other state should communicate.
Every data-backed page needs distinct loading, first-use empty, filtered-empty, error and success states. Each state should explain what happened, preserve context and offer the safest useful next action.
An empty account should teach the first successful action. A filter returning no matches should preserve the filter and offer to clear or adjust it. Using one generic empty illustration for both loses essential context.
Skeletons should approximate the final structure so content does not jump when it arrives. Avoid indefinite spinners where progressive or partial content is available.
Explain whether retry is safe, preserve the user's input, expose a support reference when useful and avoid blaming the user for service failures.
A user who can view but not edit should see why an action is unavailable. A user who cannot view the resource should receive a clear boundary without leaking sensitive record details.
Usually validate on submit or after a field has been meaningfully completed. Immediate errors can interrupt entry before the value is valid.
Usually no. Preserve the application shell and enough context to retry, go back or seek help.
Show that the dataset exists but the current query matched nothing, display active filters and offer a clear way to adjust or remove them.