Sponsored Link •
In honor of Jef Raskin, kudos to the Gmail team.
There's a school of thought in UI design (perhaps led by the late Jef Raskin) that confirmation dialogs are a bad idea.
The argument goes roughly as follows: soon, clicking "OK" after an operation that requires confirmation becomes a habit to the point where you don't read the dialog at all, and your fingers/mouse click OK without engaging your brain. So the one time when you should have had second thoughts, the confirmation dialog has already been clicked by the time you get regret.
There are a number of arguments against this POV (especially when applied in the extreme, like Jef was apt to), but we've all encountered annoying confirmation dialogs that serve no purpose except to slow down our train of thought.
Anyway, I just noticed that Gmail is using, in at least one place, an alternative that's clearly better: when you start replying to a message and decide to discard it, you can click a Discard button. Now, the Discard button is right next to the Save button, and a lesser UI designer might have used a popup dialog here to ask if you really wanted to discard the reply. But Gmail's solution is infinitely better: it removes the message editor, displaying in its place a message "Your message has been discarded. _Undo discard_" where the last part is a hyperlink that brings back the reply editor you discarded. So normally you can immediately go on with your work; but if you have regrets or are startled because you didn't mean to discard the message, you can get it back.
Way to go Gmail team!
|Guido van Rossum is the creator of Python, one of the major programming languages on and off the web. The Python community refers to him as the BDFL (Benevolent Dictator For Life), a title straight from a Monty Python skit. He moved from the Netherlands to the USA in 1995, where he met his wife. Until July 2003 they lived in the northern Virginia suburbs of Washington, DC with their son Orlijn, who was born in 2001. They then moved to Silicon Valley where Guido now works for Google (spending 50% of his time on Python!).|