3 ms·
I build front ends closely with a design/"UX" team, and this is a real thing. We intentionally add delays, especially on "save", like what the author is referri
by wildrhythms 5y ago
I build front ends closely with a design/"UX" team, and this is a real thing. We intentionally add delays, especially on "save", like what the author is referring to. People expect there to be a delay, so a UI without the delay is unexpected. We have unintentionally trained users to expect to wait for the computer to do certain tasks.
- eyelidlessness 5y agoOne thing I’ve found effective—related to where I thought this post was going before it veered off my predicted path—is instead of adding delay, changing the state of the UI element that’s being interacted with immediately. This still shows work is being done, without adding any more delay than the time it takes to change state. My expectation was that this was going to be a case where users were trained to double click, and they were triggering multiple requests that way. Of course the solution to that is to prevent the second click before it happens, and visually indicate that the button was clicked. The same approach applies here. Users expect to see state change when they perform actions.