Beyond the Progress Bar
Bars are not the only way to pass time. Explore the following alternatives to the standard progress bar, then discuss with your team: what are the advantages and disadvantages of each approach?
- indeterminate progress bar | splash screen | console output | skeleton screen | throbber
The spinning circle that tells you nothing. The company logo that greets you while an app loads. The gray placeholder boxes that fill in with real content a second later. When a true progress bar isn't possible, designers reach for these other ways to make a wait bearable — each with its own trade-offs.
Key concepts
- Determinate Versus Indeterminate
- A true progress bar is 'determinate' — it knows how far along you are. Many waits are 'indeterminate': the system can't predict the time, so these alternatives reassure you it's working without claiming to know when.
- Perceived Performance
- How fast something feels, regardless of how fast it is — a skeleton screen makes an app feel quicker by showing the shape of content immediately, though the wait is unchanged.
- Honesty Versus Comfort
- The core tension: a throbber or console output is honest but tells you little; a splash screen comforts but can hide a stall — each trades transparency against reassurance.
What to know
-
01
Which alternative fits comes down to one thing: whether the system can predict the time. A determinate bar suits a wait you can forecast; an indeterminate signal (throbber, skeleton, splash) suits one you can't — and forcing a fake bar onto an unpredictable task is exactly what breeds the maddening 'stuck at 99%'.
Keep reading the full lesson
The rest of this lesson — every key insight, the cross-subject connection, the Are We There Yet? theme tie-in, and practice questions — comes with full access.
Unlock full access →$9.99/month, or $29.99 for the whole season — see plans.
New here? Create a free account to read the free section first.