3 ms·
Now there's an interesting UX paper if it hasn't been done already. In UX we hear that a milliseconds long delay directly affects user retention rates. I wonder
by kagamine 11y ago
Now there's an interesting UX paper if it hasn't been done already. In UX we hear that a milliseconds long delay directly affects user retention rates. I wonder how users feel about search reliability, or data integrity when results are faster than expected.
- clay_to_n 11y agoI don't know about papers, but I've read writeups from companies adding a "delay", usually with a progress bar, for things that are actually near-instant to perform. For "large" seeming operations, sometimes users assume an instant response actually means a failure. DigitalOcean's Create Droplet flow comes to mind. You get a progress bar indicating your droplet is being created, but in just a few seconds you can click "My Droplets" and go use it immediately.
- talmand 11y agoI stated elsewhere that I introduced a delay for those very reasons. In that case the search functionality was reported as broken for the second search. Because the first and second test searches happened to have the same results in that particular case, but the fast response prevented an understanding that something was in fact done.