> That link doesn't contain anything that justifies adding prolonged delays to applications. It does in the context of usability: > What I remember learning w

> That link doesn't contain anything that justifies adding prolonged delays to applications. It does in the context of usability: > What I remember learning was that any latency of more than 1/10th of a second (100ms) for the appearance of letters after typing them begins to negatively impact productivity (you instinctively slow down, less sure you have typed correctly, for example), but that below that level of latency productivity is essentially flat ... > That's for visual feedback that a specific input has been received. Then there'd be a standard of responsiveness in a requested operation. If you click on a form button, getting visual feedback of that click (eg. the button displays a "depressed" look) within 100ms is still ideal, but after that you expect something else to happen. If nothing happens within a second or two, as others have said, you really wonder if it took the click or ignored it, thus the standard of displaying some sort of "working..." indicator when an operation might take more than a second before showing a clear effect (eg. waiting for a new window to pop up). > but this delay is tens of seconds. Oh, I wasn't aware of that - in that case it's ofcourse unjustified and definitely a "dark pattern".