UX Foundations · Step 5 · 6 min read
Interface states: empty, loading, error, success
A screen is never just the version in the mockup. Before there is data, while it loads, when something fails and after the job is done, people see other states. What each state should say and do, with NN/g guidance on empty states, progress indicators and error messages.
The mockup shows one moment; the product lives in many. Designers love the full screen with perfect data. But a new user first sees an empty list. Everyone sees a loading state many times a day. Networks fail. And when a task is done, people need to know it's really done. If you don't design these states, a developer will, in a hurry, with a grey "No data" and a spinner.
What you'll be able to do after reading:
- List the states a screen goes through, and design each one
- Turn an empty state into a first step
- Pick the right loading indicator for the wait
- Write error and success messages that tell people what to do next
1. One screen, several states
Say why, and offer the first step.
"No invoices yet. Create one"Show that something is happening.
Spinner, skeleton or progress barThe state most designs show.
Also test with too much contentSay what happened and how to fix it.
Keep what the person typedConfirm, and say what happens next.
A reference number, if anyTake any screen with data, for example a list of invoices. It has at least five states:
| State | When it happens | What it must do |
|---|---|---|
| Empty | No invoices yet, or a search found nothing | Explain why, and offer the next step |
| Loading | Data is on its way | Show that the system is working |
| Ideal | Data is there | The design you already drew; check it with very little and very much data |
| Error | The data didn't load, or an action failed | Say what happened and how to recover |
| Success | An action worked (sent, paid, saved) | Confirm it and say what happens next |
All five are "visibility of system status", the first of Nielsen's heuristics, in practice. See Affordances, signifiers and feedback.
2. Empty states
NN/g warns that "totally empty states cause confusion about how and whether the system is working" (NN/g, Kaplan, Designing Empty States in Complex Applications, 2021). Its three guidelines: use empty states to communicate system status, to provide learning cues, and to provide direct pathways for key tasks.
There are different kinds of empty, and each needs its own message:
- First use: "You have no invoices yet. Create your first invoice." (with the button)
- No results: "No invoices match 'Smiht'. Check the spelling or clear the filters."
- All done: "No tasks left for today."
3. Loading states
Use the response-time limits from the first lesson of this step. NN/g: "Use a progress indicator for any action that takes longer than about 1.0 second" (NN/g, Sherwin, Progress Indicators Make a Slow System Less Insufferable, 2014):
| Wait | What to show | Source |
|---|---|---|
| Under 1 s | Nothing extra; the result appears | Skeleton screens or spinners "aren't necessary" under 1 s (NN/g, Tankala, Skeleton Screens 101, 2023) |
| 1 to 10 s | A looped animation (spinner), or a skeleton screen for a full page | "Looped animation: Use only for fast actions" |
| 10 s or more | A percent-done bar, ideally with steps or time left | "Percent-done animation: Use for actions that take 10 seconds or more" |
Sherwin's article also gives a simple rule: "Always give some type of immediate feedback." A skeleton screen is a grey outline of the page that appears while content loads; NN/g says it "reduces the perceived loading time" for full-page loads.
4. Error states
An error state is the moment people most need help, and often the moment they get the least. NN/g's error-message guidelines include (NN/g, Neusesser and Sunwall, Error-Message Guidelines, 2023):
- "Display the error message close to the error's source."
- "Use human-readable language."
- "Concisely and precisely describe the issue."
- "Offer constructive advice."
- "Take a positive tone and don't blame the user."
- "Preserve the user's input."
A worked example
| Weak | Better |
|---|---|
| "Error 500" | "We couldn't load your invoices. Check your connection and try again." [Try again] |
| "Upload failed" | "This file is 25 MB. The limit is 10 MB. Try a smaller file or compress it." |
| "You entered an invalid date" | "Date of birth must be in the past" |
Not every problem is an error message. GOV.UK says not to use error messages to tell people they "are not eligible or do not have permission" (GOV.UK Design System, Error message); those need their own page with an explanation.
5. Success states
Success is easy to forget, because nothing went wrong. But people who don't see a clear confirmation often repeat the action or call support. GOV.UK's confirmation pages "reassure users that they have completed a transaction and helps them understand what to expect next" (GOV.UK Design System, Confirmation pages). They must include a reference number, if there is one, and "details of what happens next and when".
Small actions need small confirmations: a "Saved" label, a tick, a short message that disappears. Big actions (payments, applications) need a page or a message that stays.
AI features add one more state: the answer may be uncertain or wrong. See Designing for uncertainty.
6. Common mistakes
- Designing only the ideal state, with perfect data of perfect length.
- A blank screen or "No data" with no explanation or next step.
- A spinner that never stops when the network fails.
- Error codes instead of words, or errors that blame people.
- Losing what people typed when an error appears.
- No confirmation, so people pay or send twice.
7. Vocabulary
| Term | Meaning |
|---|---|
| Interface state | How a screen looks and behaves in one situation |
| Empty state | What a screen shows when there is no content |
| Loading state | What a screen shows while it waits for data |
| Skeleton screen | A grey outline of the page shown while it loads |
| Error state | What a screen shows when something fails |
| Success state | The confirmation that an action worked |
8. Try it (no tools needed)
- Pick one screen of an app you use (your messages, a shopping basket, a list of files).
- On one sheet of paper, sketch it in five boxes: empty, loading, ideal, error, success.
- Write the exact words for the empty, error and success states. Each must say what happened and what to do next.
Reflection questions: Which state did you find hardest to imagine? Which one do you think the real app designed least?
9. If you already practise
- Add a "states" row to your handoff for every screen, and review it with developers; see Handoff to developers.
- Test the ideal state with extremes: one item, a thousand items, a very long name, a missing photo.
- Keep a shared library of error and empty-state messages so the product speaks with one voice.
Checklist
Learn more
- NN/g: Designing Empty States in Complex Applications: 3 Guidelines (2021) · Progress Indicators Make a Slow System Less Insufferable (2014) · Skeleton Screens 101 (2023) · Error-Message Guidelines (2023)
- GOV.UK Design System: Error message · Confirmation pages
Books, courses and videos to go deeper
- Usability EngineeringJakob NielsenBook · Morgan Kaufmann, 1993 · chapter 5 on response times (Amazon)
- The Design of Everyday ThingsDon NormanBook · revised and expanded edition (Basic Books, 2013), on feedback and errors
Book links go to Amazon. As an Amazon Associate I earn from qualifying purchases, at no extra cost to you.
Related
Affordances, signifiers and feedback · Forms · Heuristic evaluation · Handoff to developers · Designing for uncertainty