Comments on: Interaction Design Experiment: Delete Row

By: Mike B. Fisher

Mike B. Fisher — Sun, 13 Sep 2009 18:34:30 +0000

I find that a lot of the Google products behave as though they were created by a group of very smart but slightly detached engineers. They’re often very rich in features but lack the elegant simplicity that would make them easy to learn.

By: Wayne State Web Communications Blog » Blog Archive » [Friday Links] The Design and UI Edition

Mon, 09 Feb 2009 15:33:36 +0000

[...] Interaction Design Experiment: Delete Row [...]

By: Chris

Chris — Sat, 07 Feb 2009 21:27:11 +0000

I share exactly your opinion, Jesper. No more questions but undo option (better: unlimited undo history)!
The “Never Use a Warning When you Mean Undo” article was imho one of the most important articles on ALA.

By: Jesper Rønn-Jensen

Jesper Rønn-Jensen — Mon, 02 Feb 2009 12:26:09 +0000

@prullenbak: Often I prefer the way you describe it. But it can backfire if for instance a confirmation box is required. In this case, you will end up clicking 3 are-you-sure-confirmations when deleting 3 rows.

So it really depends on the nature of the data. To take it even further, i’d like to combine your “just delete” description with ability to undo deletions. This would yield the smallest number of clicks and an ability to revert destructive actions.

By: prullenbak

prullenbak — Sun, 01 Feb 2009 22:42:13 +0000

Better yet: make it so that a click on the “delete” link, deletes the message from the list without a page refresh. Make it dissapear visually, and move the item to the trash. (even that movement could be made visual with a little AJAX). I don’t like the ‘click-three times to delete something’-approach.