Chapter #55. Use a "Linear" Progress Bar if a Task will Take a Determinate Amount of Time
Despite your iPhone having the number-crunching power of a late-1990s supercomputer, everyday tasks still seem to take a maddeningly long time in a lot of software. Printing, for example: why does it take so long for the computer to send a document to a printer? It's as if the printer has to work out how to be a printer every time. Regardless, it's a great idea to let users know how long they're going to be waiting for.
Never show a series of completing progress bars, for example:
Copying: 0...10..50..100%
Decompressing: 0..20...60..100%
Installing: 0...15...45...80...100%
Finishing up: 0...20...60...100%
That should have just been one progress bar:
A progress bar with a start and end, that gradually fills as the task completes, is the gold standard for this. There's no ambiguity and the user can get a good idea of how long this task will take, and that it's proceeding as planned.
In...