2 of 16
Choose a loading state that explains the wait
Use a skeleton when the incoming layout is predictable. An indeterminate indicator fits an operation whose duration is unknown. Use measured progress when the amount of work completed is available.
DoSkeleton shaped like the incoming content skeleton — the layout arrives before the data
Don’tSpinner replaces the whole content area spinner — a clock with no hands
Load both — the same 900ms wait, but one pane spends it teaching you the layout
Reduced motion: end states only, as your setting asks.
Before you ship
- Does the loading treatment accurately describe what is known?
- Can someone keep using content that has already loaded?
- What appears if the request fails or returns no records?