Tag Info

New answers tagged

2

The main reason for preferring Undo over Confirmation Boxes is laid out by Alan Cooper in 'About Face 2.0, The Essentials of Interaction Design' Confirmations illustrate a quirk of human behavior: They only work when they are unexpected. If confirmations are offered in routine places, the user quickly becomes inured to them and routinely dismisses ...


0

Aza Raskin wrote a great article on this subject: Never Use a Warning When you Mean Undo. He explains the psychological reasons why confirmations are inhumane while undo is better for how humans work.


2

Blocking the user is bad UX unless the operation is catastrophic (i.e. causing great damage and/or suffering)     Imagine the following scenario... You want to copy a folder full of files from one location to another so you begin the operation and the computer is nice enough to let you know that files are copying and that it will take about 2.5 ...


9

In the general case, I agree with Evil Closet Monkey: Undo creates less friction than Delete, so it is preferable. But there is at least one case where Delete+Confirm is preferable: When your users are overwhelmed. A user is overwhelmed when he wants to complete a task, but has no idea how to do it, and expects to fail. It can be so subtle that the user ...


7

There would be a third way that i actually chose to implement in a small cms ui – and the clients seem to be happy with it so far. I also wanted to avoid the confirmation message and implementing undo just wasnt an option. So instead of adding an additional step after the user already tried to delete the content, I added a step before the user does so – so ...


1

For consumer apps and websites - delete with undo option For enterprise apps that staff use at work - delete with confirmation notification This is to prevent from employees deleting important stuff accidentally. Since "undo" function normally disappears after X seconds. That way, there is a real risk of items being deleted permanently by accident. ...


2

I think the Android Gallery "filmstrip view" and its swipe-down-to-delete is a strong counter-example for the idea that "delete and undo" is preferable. It's easy to accidentally delete while trying to browse, and the same type of action (unintentional touching) that deletes can also move you away from the opportunity to undo. To me, this is a huge UX ...


29

As a counter-argument to the (well-expressed) claims already stated in other answers, confirmation dialogs should be used when an action is not performed often and difficult to reverse. A common example is installing a program on your computer: Windows machines provide this confirmation dialog any time a program requests access to your administrator ...


36

Delete with confirmation Delete with confirmation looks like this: Assuming the user tries to get from 1 to 3 (ie, she intended to perform action 2), the user has no interest in step 2b. We put delete-guards in place to reduce user errors, but if the action was intentional (which it is more often than not) step 2b is superfluous. Undo Undo, on the ...


96

The site Good-UI argues for Undo: Try Undos instead of prompting for confirmation. Imagine that you just pressed an action button or link. Undos respect the initial human intent by allowing the action to happen smoothly first and foremost. Prompts on the other hand suggest to the user that he or she does not know what they are doing by questioning their ...



Top 50 recent answers are included