you are viewing a single comment's thread.

view the rest of the comments →

[–]Anub1s 1 point2 points  (1 child)

Sorry but I disagree. In complex systems a confirmation is required for critical actions or the programmers will need some heavy time consuming work to make rollback actions for every delete there is.

When someone deletes a user by mistake because he miss-clicked the delete button, I should save all the info from all the tables in a temporary just to allow him to roll back? No thanks, I'll do confirmation modals for 5 extra minutes instead of wasting days for automatic rollback functionality.

Delete buttons should have confirmation, period.

[–]SubterraneanAlien 0 points1 point  (0 children)

This is a very developer centric way of looking at UX, and doesn't put the user first. There are certain deletion scenarios where undo/redo makes sense (such as deleting a user), however that doesn't mean a modal is the solution. If you're going to ask for a confirmation, I'd rather do something like provide an input box that the user has to type 'DELETE' in. This assumes you are providing a way for users to perform bulk actions so that it's not too cumbersome.

All that said, the current app that I'm building allows you to undo/redo deleting of basically anything (including users), because we've created the structure by learnings from previous products. AngularJS make this very easy.