Make Progress Visible: Show Users the Wait Is Working
People stop trusting an app that goes quiet. Learn the time limits, the right indicator, and how to keep progress honest.
In short
Making progress visible means showing users that an app is still working during a wait, so they keep trusting it instead of thinking it went quiet.
4 min readFree
Why users need to see progress
Every app makes people wait now and then. A file saves, a page loads, or a search runs. During these moments, the person looking at the screen asks one simple question: is anything happening?
A progress indicator answers that question. It is a visual sign, such as a bar or a spinning circle, that shows work is still going on. Nielsen's guidance says such signs do three jobs: they show the app is working, they hint at how long the wait will be, and they give the eye something to watch.
Without any sign, a slow task can look broken. Progress indicators reassure people that the system has not crashed, and they may do other things while they wait.
Key words
- Progress indicator
- A visual sign, such as a bar or spinner, that tells people work is under way.
- Feedback
- Any signal from the system that reacts to what a person did or is doing.
- Response time
- The gap between a person's action and the system's reply.
- Percent-done indicator
- A bar or number that shows how much of a task is finished.
- Determinate
- The task length is known, so the indicator can fill up by a true amount.
- Indeterminate
- The task length is unknown, so the indicator only shows that work continues.
What are the three time limits for waiting?
Usability expert Jakob Nielsen popularised three response time limits. They describe how people feel a delay, which is why they still guide designers. Use them to decide how much feedback to add.
The three limits
0.1 second
Under this limit, the screen seems to react at once. The person feels they are touching the object directly, so only the result needs to appear.
1 second
Around one second, people notice the pause, yet their train of thought stays on track. The task still feels connected to what they did.
10 seconds
Past about ten seconds, attention drifts away. Nielsen's guidance says users should get feedback on when the computer expects to be done, and percent-done indicators suit operations over about ten seconds.
How do you choose the right indicator?
- 1
Check the wait length
If the answer comes in well under a second, a plain result is enough. For waits from about one second up toward ten, show clear progress and say what is happening.
- 2
Use a bar when you can measure
Apple advises using a determinate progress indicator when possible, and says determinate indicators suit tasks with a well-defined duration. A bar suits work with a clear total, such as a file upload.
- 3
Show a count when the total is unknown
If you cannot know the total, show running progress, such as how much work is done so far.
- 4
Keep the spinner moving
A spinner only shows that the app is working, not how far it has got. Keep it animated, because a still indicator can look frozen.
How do you keep the signal honest?
A progress bar makes a promise. If it races ahead and then crawls for minutes, people lose trust in it. Good progress should match the real work, so the pace feels steady.
Apple asks developers to be as accurate as possible when reporting progress, and notes that uneven pacing can make people wonder whether the app is working and can feel deceptive.
Tip
Keep the pace even. A bar that moves at a steady speed builds more trust than one that jumps to most of the way and then stalls.
Try a text progress bar
This short Python sample prints a text progress bar. It uses only the standard library, so it prints the same text every time it runs.
total = 10
for done in range(0, total + 1, 2):
percent = done * 100 // total
bar = "#" * done + "-" * (total - done)
print(f"[{bar}] {percent}%")Output
[----------] 0% [##--------] 20% [####------] 40% [######----] 60% [########--] 80% [##########] 100%
Each line shows one step. The hash marks are finished work and the dashes are work still left. The // symbol divides and keeps only the whole number, so the percent stays a clean integer.
Check what you learned
Quick check
A file is uploading and its total size is known. Which indicator fits best?
Key takeaways
Show work
Any wait longer than a moment needs a sign that the app is still working.
Match the sign to the wait
Short waits need little. Longer waits need a bar, a count, or a moving spinner, and very long waits need a way to stop.
Stay accurate
Show real progress at a steady pace. Never fake it to look busy.
Sources
Last updated on 17 November 2026
Related lessons
Learn with me
Every lesson is free. I add new ones as I learn. Have a question, or want help with your own work? Book a short call.