4 ms·
https://www.nngroup.com/articles/ten-usability-heuristics/ https://www.nngroup.com/articles/ten-usability-heuristics/ https://asktog.com/atc/principles-of-inte
by ProxCoques 8y ago
https://www.nngroup.com/articles/ten-usability-heuristics/ https://www.nngroup.com/articles/ten-usability-heuristics/
https://asktog.com/atc/principles-of-interaction-design/ https://asktog.com/atc/principles-of-interaction-design/
- oldcynic 8y agoThat's something entirely different, and very well known. I can't find any reference to providing a delay before you truly perform an action, but allowing undo for that time. Relevant to delete / undo they talk of the preference for an undo (eg ^Z at any time) to "Are you sure?". No mention of delaying action or availability of undo. Then preference for consistency of action - within app and generally, not deviating from common expectations (eg that a trash can allows restore), and recommendations for visual feedback when latency and delay is involved. None of which fits the original temporary delay/undo.
- ProxCoques 8y agoOn the web, it is extremely difficult to have an undo stack, so I'm talking about "undo" as implemented by appearing to do the action (eg delete), but delaying its actual action while giving the user the ability to undo it. If they take no action (or navigate away, etc.) the action is done. In both of those links I posted, it clearly states well-designed systems have undo.