Interactions · Status feedback
Loading State
Also called: Loading, Loading indicator, Pending state
Feedback shown while data or an action isn't finished yet. Common forms are spinners, skeleton screens, progress bars, and buttons in a loading state.
In detail
Any time there's a wait, let the user know "the system is working, it hasn't frozen." Different cases call for different forms. When a whole block of content loads for the first time, use a Skeleton: gray blocks in the rough shape of the content. For partial refreshes or short waits, use a spinner. For long tasks where you can calculate progress (like uploads), use a progress bar. After a submit click, put the button itself into a loading state and block repeat clicks.
Requests that finish quickly (within 300ms) can skip the loading indicator so the UI doesn't flicker. Design the loading state separately from the empty state and the error state too. Still loading, no data, and something went wrong are three different screens.
When you ask AI for this, say which kind of loading indicator to use, where it goes, and which actions to disable while loading.
Developer infoTerm ID, DOM cues, match priority
- Term ID
interaction-loading-state- DOM selectors
- No DOM cues. This concept isn't detected directly on a page.
- Priority
- 1 · when several match at the same level, the higher priority wins
- Version
- v1 · updated Sep 29, 2026