Empty states and error messages that help
How to design empty screens and error messages that tell people what happened and what to do next, with before and after wording examples.
The screens that get the least design attention are the ones people see when something is missing or broken. An empty list. A failed payment. A search with no results. These moments decide whether someone keeps going or gives up, and they are usually written by whoever was closest to the keyboard at the time.
A little care here goes a long way. It is mostly a writing job, and it costs very little.
What is an empty state?
An empty state is what a screen shows when there is nothing to display yet. A new customer's order history. A booking calendar with no appointments. A favourites list nobody has added to.
There are three kinds, and each needs a slightly different message:
- First use. The person is new and has not done anything yet.
- Cleared. They have finished everything, such as an inbox with no unread messages.
- No results. They searched or filtered and nothing matched.
The lazy version of all three is a blank white screen, or the words "No data". That leaves the person wondering whether the app is broken, still loading, or simply empty.
What should an empty screen say?
A good empty state does three jobs: it explains what would normally be here, reassures the person that nothing is wrong, and offers the obvious next step.
Here are some rewrites for a cafe ordering app.
Order history, first use
- Before: "No orders."
- After: "Your past orders will appear here, so you can reorder your usual in one tap." Followed by a button: "See the menu".
Search, no results
- Before: "0 results found."
- After: "Nothing matches 'chai latte'. Check the spelling, or browse all hot drinks." With a link to the category.
Notice the pattern. Say what belongs here, then give people somewhere to go.
Why are most error messages so bad?
Because they are written from the system's point of view. "Error 422: unprocessable entity" is accurate from the server's perspective. To a customer trying to book a haircut, it is gibberish with a hint of blame.
Bad error messages share a few habits:
- They are vague. "Something went wrong."
- They are technical. Codes, jargon, the word "invalid".
- They blame the user. "You entered an incorrect value."
- They offer no way forward. Just an "OK" button, as if anything were OK.
A formula for plain error wording
Every error message should answer three questions, in this order.
- What happened? In everyday words.
- Why, if it helps? Briefly, and only if the reason is useful.
- What can I do now? One clear action.
Some before and after examples:
Payment declined
- Before: "Transaction failed. Error code 51."
- After: "Your card was declined. No money has been taken. Try another card, or contact your bank."
Form field
- Before: "Invalid input."
- After: "Enter your mobile number as 10 digits, starting with 04."
Time slot taken
- Before: "Booking could not be completed."
- After: "Someone just booked 2:30 pm. The next free times are 3:00 pm and 3:30 pm."
The payment example includes a detail worth copying: "No money has been taken." When an error involves money or personal information, people's first worry is what just happened to it. Answer that before anything else.
Where and when should errors appear?
Wording is half of it. Placement and timing are the rest.
- Show the message next to the problem. If the email address is wrong, the message goes under the email field, not in a banner at the top that the person has to scroll back to find.
- Check as people go, gently. Tell them the password is too short when they leave that field, not after they have pressed "Submit" on a twelve field form.
- Never wipe what they typed. Clearing a form after an error is the quickest way to lose a customer.
- Keep the tone level. Calm and factual. Save the jokes. "Oopsie! Our hamsters fell off the wheel" is charming once and grating when your payment has failed three times.
Better still, prevent the error. Grey out times that are already booked. Offer a date picker instead of asking people to type a date in a set format. Accept phone numbers with or without spaces. Every error you design out is one you do not have to word.
An audit you can do this week
Go through your own app or website and deliberately break things. It takes about an hour, and most owners have never done it.
- Open every list or history screen as a brand new user. Is each one blank, or does it explain itself?
- Search for something that does not exist.
- Submit each form empty, then with a wrong email and a wrong phone number.
- Turn on aeroplane mode halfway through a task.
- Try to book or buy something that is unavailable.
For each message you find, ask the three questions: does it say what happened, why, and what to do next? Write down the ones that fail and rewrite them in plain words. Hand that list to your developer. Changing text is among the cheapest fixes there is, and customers notice the difference straight away.