Lots of design advice advocates for this kind of linear process indicator design (progress should never stop bc user must be kept happy, indicator should always exaggerate wait time)
-
-
-
any good link?
- 1 more reply
New conversation -
-
-
A microcosm of the software development process itself. Steady easy progress, occasional unexpected quick wins and inevitable dreaded stop-the-world pauses during which no one knows what the hell is going on
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Relativistic? More like random in an extrapolational statistics mixed with unexpected factors sense.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
What users want: steady, deterministic countdown that decrements by 1.1 minutes every 60 seconds. What devs can provide: extrapolation based on recent progress rate. It’s really hard to design a countdown that’s accurate, much less one that’s accurate and non-frustrating.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
All time is relative. Ever been really hungry and had to wait to eat? Or been in a class with a very bad teacher? Or in just about any meeting, ever.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Bram Cohen's story about implementing BitTorrent's progress bar was fun to read. Absolutely impossible to do accurately and in a user-friendly way.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.