Loading state

Also called loading UI or loading indicator

The view a screen shows while its data is on the way, designed together with the outcomes that follow: loaded, empty, or error.

What is Loading state?

Any screen that fetches data passes through a loading state before it shows anything useful. Common choices are a skeleton screen (gray shapes in the layout of the coming content), a spinner, or a progress bar. It is often the first thing people see, so it shapes how fast the app feels.

Plan it together with the three outcomes that can follow: loaded with data, empty (the request worked but there is nothing yet), and error (the request failed). Each needs its own design. An empty inbox should say so and suggest a next step, and an error should explain what happened and offer a Try again button.

Show a skeleton when you know the shape of the content, and a spinner for short actions like saving. Wait 200–300ms before showing any indicator so fast responses don’t flash, and keep the container the same size across states so the page doesn’t jump. Mark the region with aria-busy="true" while it loads so screen readers know to wait.

Often confused with

Skeleton screen
A skeleton screen is one way to show a loading state: gray placeholder shapes in the layout of the content that is coming.
All terms

Skeleton screen

A loading placeholder made of gray blocks shaped like the content on its way, often with a soft shimmer, that the real content replaces.

Spinner

A small looping animation, usually a rotating ring, that shows the app is busy with a short task of unknown length.

Empty state

What a screen shows when there is nothing in it yet: a short message, often a simple illustration, and one clear action to add the first item.

Perceived performance

How fast an app feels to people, which skeleton screens, instant feedback, and progressive loading can improve even when the real wait stays the same.