Tithi Mondal

Article6 min readUpdated

Empty State Design: Loading, Error and No Results Screens

Empty state design for the screens most products forget: error screens, loading states, skeleton loaders and no results pages, with example wording.

By Tithi Mondal, UI/UX Designer

Read inहिन्दीবাংলাमराठीதமிழ்తెలుగుગુજરાતી

Empty State Design: Loading, Error and No Results Screens: cover illustration

A new user installs your food ordering app. They open the Orders tab to see their history. The screen is white and completely blank. There is no message, no picture, no button. They wonder if the app is broken. Some will close it and not return.

That blank screen is an empty state. It is one of the screens most products forget. The same is true for loading screens, error screens and the page that shows when a search finds nothing. Designers spend weeks on the home screen and an hour on these. Yet every user sees them, often at the exact moment they are unsure or frustrated.

This post covers empty state design, no results pages, loading screen UX with skeleton loaders, and error screen design. For each, I give the rules I follow and examples of good wording.

The four situations and what each needs

SituationThe user is thinkingThe screen must do
Empty state"Is anything here?"Explain, and show the next step
No results"Did I search wrongly?"Help them try again
Loading"Is it working?"Show progress, calm them
Error"What went wrong, what now?"Say what happened and how to fix it

Each screen has the same three parts: a short headline, one line of help and one clear action. A small picture is optional.

Empty state design

There are three kinds of empty state, and each needs different words.

First use. The user has not done anything yet. The screen should explain what will appear here and push one action.

  • Orders tab: "No orders yet. When you order, you can track it here." Button: "Browse restaurants".
  • Class schedule: "No classes booked. Pick a class to join live." Button: "See classes".
  • Seller listings: "You have not added a product. Add your first product to start selling." Button: "Add product".

Cleared by the user. The user finished something, such as an inbox or a task list. The tone can be light.

  • "All done. You have no pending approvals."

Nothing to show for now. Data is not available yet, such as a report with no data in the first week.

  • "Reports appear after your first week of classes. Check back on Monday."

Rules for empty states:

  1. Say why it is empty, in plain words.
  2. Give one primary action. Not three.
  3. Do not blame the user. Never write "You have nothing".
  4. Use a small illustration only if it adds clarity. A picture that says nothing is decoration. When you do use one, keep one style across every empty screen.
  5. Make the empty state look different from a loading state. A blank page can be confused with one that is still loading.

I think of first-use empty states as part of onboarding. The user is learning what the app can do. The ideas in app onboarding UX best practices apply to them.

No results page

A no results page appears after a search or a filter. The user already tried something, so the page should help them try again. A dead end is the worst design here.

Good wording and actions:

  • Headline: "No results for 'paneer tikka masala'". Repeat their words, so they know the search was read.
  • Help: "Check the spelling or try a shorter word like 'paneer'."
  • Action: a button to clear filters, and some suggestions such as popular items or categories.

If filters caused zero results, say so: "No restaurants match all your filters. Remove 'Open now' to see 14 more." Only show a count like that if the app can truly calculate it.

For regional users, remember that many people type in mixed language or in Roman letters for Hindi or Bengali words. A search that returns nothing for a spelling variation feels broken. Where possible, handle common spelling variants and suggest the closest match.

Loading screen UX and skeleton loaders

A loading state appears while the app fetches data. On a mid-range phone with a slow network, this can last several seconds, and this is common outside big cities. I cover the wider topic in designing for low-end phones and slow networks.

Choose the tool by how long the wait is.

  • Under a second: show nothing special. A flash of a spinner looks worse than a short wait.
  • A few seconds: show a skeleton loader. This is a grey outline of the screen, with boxes where text and images will appear. It tells the user what is coming and keeps the layout from jumping.
  • Longer waits: show a progress bar or a message, such as "Finding the best fares". For uploads, show the percentage.
  • Very long waits: let the user leave and come back, and tell them you will notify them.

Tips for skeleton loaders:

  1. Match the real layout. A skeleton with the wrong shape feels like a trick.
  2. Use a soft grey and, if you like, a slow light movement across it. Avoid fast flashing.
  3. Show the parts that are ready. Header and navigation should appear at once.
  4. Never leave a spinner with no end. After a set time, show an error with a retry button.

A plain spinner is not wrong. It is the right tool for a short action, such as saving a form. Use a skeleton for page content.

Error screen design

An error screen has the highest emotional cost. Money, documents or time may be at risk. The user needs three things: what happened, whether their data is safe and what to do now.

Compare these:

  • Poor: "Error 500. Something went wrong."
  • Better: "We could not load your orders. Your orders are safe. Check your internet and try again." Button: "Try again".

For a payment failure, clarity matters most. Suppose a UPI payment times out:

  • "Your payment is still pending. If money was deducted, it will return to your account or the order will confirm. Check the status in a few minutes." Buttons: "Check status", "Try another way".

I would not say how many days a refund takes unless the business has confirmed it. This also touches UPI payment UX and checkout design.

Rules for errors:

  1. Say what happened in human words, with no codes in the main message. Put the code in small text for support.
  2. Tell the user their work is safe, if it is.
  3. Give a way forward: retry, go back, or contact support. A WhatsApp support link is useful in India.
  4. Keep the tone calm. No exclamation marks, no jokes when money is involved.
  5. Handle specific cases: no internet, server problem, session expired, permission denied, form errors. A single "Something went wrong" for all of them is not helpful.
  6. For form errors, show the message next to the field and say how to fix it: "Enter a 10 digit mobile number", not "Invalid input".

Writing these screens well

The words on these screens are called microcopy, which means the small pieces of text inside an interface. A few habits help:

  • Use the same tone as the rest of the app.
  • Write the action as a verb: "Add product", "Try again", "Clear filters".
  • Test the text with translation, because many users will read a translated version. Short and literal phrases survive best. See UX writing and microcopy for apps.
  • Build a list of every empty, loading and error state before development starts. It is easy to find 20 or more in a normal app.

When I map the flow of an app, I list these states next to the main screens, so they are designed rather than left to default. A UX audit often finds them missing. If you would like these screens planned into your product, I cover them in my UI/UX design work.

Frequently asked questions

What is an empty state in an app?

It is the screen a user sees when there is no content to show yet, such as an orders tab before the first order. A good empty state explains why it is empty and gives one action.

When should I use a skeleton loader instead of a spinner?

Use a skeleton loader when a whole page or list takes a few seconds to load, because it shows the layout that is coming. Use a spinner for short actions such as saving a form.

How should an error message be written?

Say what happened in plain words, tell the user if their data is safe, and give a way forward such as Try again or a support link. Avoid codes and blame in the main message.

Working on something like this?

Tell Tithi what you are planning. You get a clear scope, a fixed price and a timeline before any work begins. I reply to every enquiry within 24 hours.

Your details go only to Tithi and are used only to reply to you. No newsletters, no sharing.

Have a product in mind? Let us design it properly.

Tell me what you are building. I will reply with questions, a rough timeline and a quote.