Loading & Progress
Waiting is part of every product, and how a product handles it shapes whether it feels fast. A spinner that flashes for a quarter second reads as a glitch. A progress bar stuck at 90% reads as broken.
None of this topic’s stats is contested. All 13 systems that address it show nothing for very short waits, most often until about a second has passed. All 8 that cover progress show a percentage or steps whenever progress can be measured, and 13 of 14 put the loading state inside the button whose action is running. Skeletons are the one real divide. 6 of 10 use them for content loading for the first time, and the other 4 document only spinners.
- systems tracked
- 19
- sources cited
- 20
- evidence cards
- 132
- questions tallied
- 6
Popular questions
Each one is researched across every system we track. Pick one and it opens in chat, ready to send.
Systems tracked
The same core design systems are tallied on every topic, so answers compare like with like. See every source
- GOV.UK
- IBM Carbon
- Shopify Polaris
- Google Material 3
- Atlassian
- GitHub Primer
- Adobe Spectrum
- Microsoft Fluent
- Salesforce Lightning
- Ant Design
- Mozilla Acorn
- Stripe Apps
- shadcn/ui
- Porsche Design System
- Base Web
- GitLab Pajamas
- Radix UI
- USWDS
- Pinterest Gestalt
Got a loading & progress question?
Your first 3 questions are free. Every answer comes with the sources behind it.