4 ms·
> Users often perceive aesthetically pleasing design as design that’s more usable. Figures that would be rule number one. Everywhere you go there are pretty UI
by kazinator 6y ago
> Users often perceive aesthetically pleasing design as design that’s more usable.
Figures that would be rule number one. Everywhere you go there are pretty UI's that are garbage, functionally.
Animation, transparent fading, no distracting scroll-bars or borders, wrapped around a 1-2-3 menu selection.
> Productivity soars when a computer and its users interact at a pace (<400ms) that ensures that neither has to wait on the other.
That is just nonsense. Productivity soars the faster the computer is. Ideally, the user should never waits for the computer; everything should be instant.
Whether the user waits for the computer is neither here nor there.
The ultimate computer-does-not-wait-for-the-user is to have the users prepare job specifications entirely outside of the computer and then submit them to a clerk at a job window. The computer never waits for a user because the job queue is busy from numerous users. It is not very good UI.
In an actual interactive UI, a needless delay could be caused by, for instance, collecting the necessary parameters for an operation through a cascade of multiple dialogs instead of batching them together. Though the computer waits more, too, that's irrelevant; the user's time is what was wasted.
I'm amazed anyone pretending to be a UI person would even feign being interested in how much time the machine spends waiting for the user.
- wtracy 6y agoThe 400 ms threshold cited for the Doherty threshold is from a 1982 research paper. I imagine that in 1982, 400 ms response times felt pretty darn good. Also, the nature of the tasks that users performed in 1982 may have meant that there was no benefit to <400ms response times. (If it takes twenty seconds to read and understand the output, and another ten to key in your next command, then a 400 ms delay is not a meaningful productivity drag.) Today, I would guess that the threshold is closer to 50 ms. (Also, "time spent by the computer waiting for the user" makes sense in the context of a 1982 research paper. That has changed in the last 28 years, to say the least.) All of this is a long way off saying that if you are making UX decisions based on 28 year old research, you are on shaky ground!
- FridgeSeal 6y agoI agree, 400ms is a long time. I’d be over the moon if most websites did things within 50ms, even 100ms would be a significant and welcome improvement. Anecdotally, when I’m working on the database at work, the olap database (Clickhouse) feels amazingly snappy because it’ll respond in around 30-60ms, but SQL server feels like molasses, even when doing queries each dB is designed for.
- kazinator 6y ago1982 was 38 years ago, not 28. The microcomputers I used in 1982 had instantaneous response time. Most of the software was developed by assembly language die-hards. 400 ms is more acceptable if there is no jitter in it, in comparison to unpredictable response time.