Bluehost.com Web Hosting $6.95

Re: [PHP] Intuitive Interfaces (was: Add Reply-To to this list(s))

This is a discussion on Re: [PHP] Intuitive Interfaces (was: Add Reply-To to this list(s)) within the PHP General forums, part of the PHP Programming Forums category; Hello Now that the discussion is coming around to be more on topic I have some stuff to add. First ...


Go Back   Usenet Forums > PHP Programming Forums > PHP General

FAQ Members List Calendar Search Today's Posts Mark Forums Read
  #1 (permalink)  
Old 11-26-2003
SLanger@spirit21.de
 
Posts: n/a
Default Re: [PHP] Intuitive Interfaces (was: Add Reply-To to this list(s))

Hello

Now that the discussion is coming around to be more on topic I have some
stuff to add.

First and most important: There is no such thing as INTUITIVE when it
comes to interfaces.
Every interface built for human machine interaction has to be learned by
the human using it. So what we consider intuitive is merely the way most
people are used to dealing with stuff. An example: The way we navigate the
computer mouse, keyboard montior seems intuitive for us but everybody had
to learn it at some point but we have gotten so used to it and navigation
by clicking on a gui that we think it as intuitive. (wouldn't it be more
intuitive to simply tell the computer what to do?!)
Another example: The discussing about reply-to header.

So what is the point of stating this?
Never assume anything as being intuitive. Investigate the way people use
your interface and improve accordingly. If you implement a function that
requires the user to learn something tell him clearly that he has to learn
it first and tell him why you are doing it this way.

Just my two cents

Stefan Langer



Reply With Quote
  #2 (permalink)  
Old 11-26-2003
John W. Holmes
 
Posts: n/a
Default Re: [PHP] Intuitive Interfaces (was: Add Reply-To to this list(s))

SLanger@spirit21.de wrote:

> So what is the point of stating this?
> Never assume anything as being intuitive. Investigate the way people use
> your interface and improve accordingly. If you implement a function that
> requires the user to learn something tell him clearly that he has to learn
> it first and tell him why you are doing it this way.


An additional point that (I think) was brought up on here a while is to
log your validation errors. This way you can determine where users have
having trouble with your interfaces or where you may have missed
something in your validation (like allowing a - in names, for example).
Now, you probably don't want to do this all of the time, but when
deploying something new or after a significant change, it's not a bad idea.

--
---John Holmes...

Amazon Wishlist: www.amazon.com/o/registry/3BEXC84AB3A5E/

php|architect: The Magazine for PHP Professionals – www.phparch.com
Reply With Quote
Reply
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are Off
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On




All times are GMT +1. The time now is 05:03 AM.


Powered by vBulletin® Version 3.7.3
Copyright ©2000 - 2009, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO 3.0.0