On 11/06/2010 06:03 AM, Cédric Beust ♔ wrote:
With a Back button, the cognitive dissonance would actually be much
lower. It's the perfect illustration of"Don't make me think"
<http://www.amazon.com/Think-Common-Sense-Approach-Usability/dp/0789723107>.
Partially agree and partially not. I mean, there are actually a lot of
places where back makes sense. I'm extensively using it e.g. in my
Android application. But there are cases in which it starts not making
sense, for instance when you perform non reversible operation. The "pay"
page is a typical example. Note that since nobody can block the back
function in a web browser, everybody providing a pay service is forced
to print in flashing colors "DO NOT PUSH BACK UNTIL THE OPERATION IS
COMPLETE". So, while it makes sense to provide back functions, it also
makes sense to disable them at least in some places.
--
Fabrizio Giudici - Java Architect, Project Manager
Tidalwave s.a.s. - "We make Java work. Everywhere."
java.net/blog/fabriziogiudici - www.tidalwave.it/people
fabrizio.giud...@tidalwave.it
--
You received this message because you are subscribed to the Google Groups "The Java
Posse" group.
To post to this group, send email to javapo...@googlegroups.com.
To unsubscribe from this group, send email to
javaposse+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/javaposse?hl=en.
