[DUG] Graphical User Interface Design

[Steve Peacocke]

Agree John,

I'll also reiterate what you may have been saying without saying it...

CONSTANCY. If it acts this way on this screen, then it should act the
same way on ALL screens.

Follow Microsoft's ever-changing "standards".

>From the Microsoft unofficial book of Confusion ^H^H^H^H^H^H^H^H^H
Customer Presentation, here is Microsoft's own list of guidelines.

1. Assume all users are idiot grandmo/fathers using the
computer/printer/thing for the first time.

2. When idiot grandmo/fathers are starting to come to grips with
simple basic usage, change the interface standards (e.g. see note in
the Secret Microsoft Internal Jokes Book #3690 - "Remove the menus
from all programs - and they think we wouldn't do that!")

3. Ask "Are you sure" questions for simple and obvious changes but
ensure very large important changes can be done without the user's
knowledge - examples from the above mentioned "Internal Jokes" book:

  3a. Allow a user to accidentally move and drop entire directory
structures into other directories without prompt or ability to reverse
and hopefully without them realising what they have done or where the
directory started from so it can be moved back.

  3b. Allow accidental removal of toolbars so the above mentioned
grandmo/fathers can call their grand/children at 2:30 am
(grandmo/fathers don't sleep at night, that's what afternoons are for)
to ask for help because their "little programs have gone from Word on
their printer and they can't get their thing from the screen where
they saved it" (sigh - yes, that is a first hand experience, don't
tell me you haven't had one of those calls).

well.. you get the idea.

HERE'S MY RECOMMENDATIONS:

1. Consistency throughout the program; consistency with Microsoft
Office programs

2. Watch the user - but watch more than one (s/he may be an actual idiot).

3. ensure common sense prevails - but make sure it is "common" sense.

4. Never, ever, EVER, clutter the screen with too much information -
try using a wizard or tabsheet or a totally seperate screen for some
of that information.

5. Personally, I always create Modal screens which means that the user
has asked to do this - then the user can't also ask to do something
else that conflicts half way through.  ... I just read that sentance
and didn't understand it either, its not just you. Er.. "I always use
Modal screens, perhaps you might consider that too".

6. Remember that a user wants to get things done - not look at pretty
colours or time your routines so they can go "Wow". Concentrate
therefore on helping the user get things done.

I'm sure other can add to that.

Steve

-- 
Steve Peacocke
http://stevepeacocke.blogspot.com/


On 28/06/07, John Bird <johnkbird at paradise.net.nz> wrote:
> Well that's the start of a big discussion!
>
> Quickly off the top of my head:
>
> Its good to use someone with an eye for visual composition as in
> photography/painting to look over the layout of the screen.
>
> Use the alignment stuff supplied in the IDE
>
> Make some overall design decisions - eg I tend to put prompts and info in
> black, and all client data in Navy as its an obvious cue to the user which
> is "their" stuff.
>
> The most useful single component is the XP Manifest and the D2007 Vista
> equivalent, all the standard VCL components look up to date and slick then.
>
> I often have groups of components set visible:=false until needed -
> simplifies the screen.
>
> *and*  sit quietly and watch users using it - that is always a lesson on
> what you thought was obvious that confuses them!
>
> John Bird
>
> Hey guys,
>
> Just about to update one of our main apps and thinking about just
> rebuilding it from the ground up, especially the gui side of it. The
> original one wasn't to bad, but looking at other programs there is some
> very nice looking applications out there. Now I have the TMS component
> set and there are some very nice graphical components in there - but I
> don't want the program to be overwhelming (picture someone that finds
> the transitions in a slide show app for the first time!) but also don't
> want it to look like something from windows 3.1
>
> End of the day it comes down to the usability for the user and making
> everything as easy and logical for them to use, but also want it to look
> appealing.
>
> So what steps, guidelines, approach do you take when designing an
> application.
>
> :-)
> Cheers
> Nick
>
> _______________________________________________
> NZ Borland Developers Group - Delphi mailing list
> Post: delphi at delphi.org.nz
> Admin: http://delphi.org.nz/mailman/listinfo/delphi
> Unsubscribe: send an email to delphi-request at delphi.org.nz with Subject:
> unsubscribe
>
> __________ NOD32 2245 (20070506) Information __________
>
> This message was checked by NOD32 antivirus system. http://www.eset.com
>
>
> _______________________________________________
> NZ Borland Developers Group - Delphi mailing list
> Post: delphi at delphi.org.nz
> Admin: http://delphi.org.nz/mailman/listinfo/delphi
> Unsubscribe: send an email to delphi-request at delphi.org.nz with Subject: unsubscribe
>