3 ms·
No such thing as too fast. If a user is confused about the interaction because of how fast it is, then that's a UX problem to fix. Speed is one of the most imp
by mcqueenjordan 7y ago
No such thing as too fast. If a user is confused about the interaction because of how fast it is, then that's a UX problem to fix.
Speed is one of the most important properties of exceptional user experiences.
I'm building a developer tool and I'm ruthlessly optimizing for speed. Waiting 20ms for a CLI command versus 100-300 is a huge difference.
- afiori 7y ago> If a user is confused about the interaction because of how fast it is, then that's a UX problem to fix In some cases the confusion comes from a "did this do any work at all" question. like git branching compared to svn for big projects. As other have brought up, instantaneous reply in airline comparison sites can cause concern of how deep the search was. A similar paradox is with psychiatrist hourly rates or the placebo effect. The high price (delay) is part of the therapy (interface).
- TeMPOraL 7y agoHaving your program sit in the chair and twiddle its thumbs to make it seem like it's working is just one possible solution. It's tragedy-of-the-commons-esque, because it perpetuates the myth that a given category of work has to be slow. Alternatives would include: results speaking for themselves, or saying something like "Searched all 124,568,902 connections", or otherwise reaffirming users the work has been done without making them pay for it with time.