navigation if it is difficult to use, it will not be used (simple, huh?) user needs to know: where...

18
Navigation If it is difficult to use, it will not be used (simple, huh?) User needs to know: where am I? where have I been? who am I? where can I go from here? how can I get there? Care about Usability

Upload: cody-nicholson

Post on 25-Dec-2015

215 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Navigation If it is difficult to use, it will not be used (simple, huh?) User needs to know: where am I? where have I been? who am I? where can I go from

Navigation

If it is difficult to use,it will not be used (simple, huh?)

User needs to know: where am I? where have I been? who am I? where can I go from here? how can I get there?

Care about Usability

Page 2: Navigation If it is difficult to use, it will not be used (simple, huh?) User needs to know: where am I? where have I been? who am I? where can I go from

How to measure Usability?

speed of performance of some activity

incidence of errors while performing act.

user’s ability to recover from errors

task magnitude in learning to use the system

user’s retention of learned skills

user’s ability to customize the system

user’s satisfaction with the system

You have arrived when the user thinks: “Interface? What interface?”

Page 3: Navigation If it is difficult to use, it will not be used (simple, huh?) User needs to know: where am I? where have I been? who am I? where can I go from

Navigation Tools

Why do you need to plan your navigation? Location: “Where am I now?” Options: “Where can I go from here?” Path: “How do I get there?” History: “What have I already explored/learned?” Microworld: “How much more is there to explore?”

Node structures

Navigation aidsBoston

Boston

Page 4: Navigation If it is difficult to use, it will not be used (simple, huh?) User needs to know: where am I? where have I been? who am I? where can I go from

Node Structures & Navigation Aids

Linear circular

Jump-linear wheel

Rooted tree general tree binary tree

Network

Single-frame techniques

Combination

Menus

Navigation maps

Metaphors

Histories

Travel buttons

Progress indicators

Page 5: Navigation If it is difficult to use, it will not be used (simple, huh?) User needs to know: where am I? where have I been? who am I? where can I go from

Node structure: Linear/Circular

Follows predefined path

Good for zooming in/out sorted list animation sequence

Page 6: Navigation If it is difficult to use, it will not be used (simple, huh?) User needs to know: where am I? where have I been? who am I? where can I go from

Node structure: Wheel

Predefined path with interruption

Good for: sorted and unsorted list list slide show continuous animation

Page 7: Navigation If it is difficult to use, it will not be used (simple, huh?) User needs to know: where am I? where have I been? who am I? where can I go from

Node structure: Rooted tree

Most intuitive navigation

Good for hypertext web browsers without maps organization chart hierarchies games with choices decisions

Page 8: Navigation If it is difficult to use, it will not be used (simple, huh?) User needs to know: where am I? where have I been? who am I? where can I go from

Node structure: Rooted tree (2)

Warning: jumping between cousin and uncle nodes

is particularly confusing people lose the hierarchical intuition

Page 9: Navigation If it is difficult to use, it will not be used (simple, huh?) User needs to know: where am I? where have I been? who am I? where can I go from

Node structure: Network

Most general structure

Good for adventure games web browsers with maps

Page 10: Navigation If it is difficult to use, it will not be used (simple, huh?) User needs to know: where am I? where have I been? who am I? where can I go from

Node structure: Framing (front-end)

Ultimate navigation (seems non-existent)

Display windows (e.g. lexicon)

Filtering (e.g., in FIND)

Sub-screen detailing (e.g., zooming,

see & point)

Page 11: Navigation If it is difficult to use, it will not be used (simple, huh?) User needs to know: where am I? where have I been? who am I? where can I go from

Combination of Node structures

Case study: Broderbund kids’ Books

Page 12: Navigation If it is difficult to use, it will not be used (simple, huh?) User needs to know: where am I? where have I been? who am I? where can I go from

Navigation Aids

MenusWhen to use:

Navigation maps When to use:

MetaphorsWhen to use:

HistoriesWhen to use:

Travel buttonsWhen to use:

Progress indicatorsWhen to use:

Page 13: Navigation If it is difficult to use, it will not be used (simple, huh?) User needs to know: where am I? where have I been? who am I? where can I go from

Navigational Aids: Menus

Full screen menus: explicit options text-only menus text & graphics menus graphics-only menus

Hidden menus: options Pull-down menus Pop-up menus

Page 14: Navigation If it is difficult to use, it will not be used (simple, huh?) User needs to know: where am I? where have I been? who am I? where can I go from

Navigational Aids: Maps

One of the best navigational aids

They show the big/whole picture contents structure Linkage

The WWW cannot implement them easily

Page 15: Navigation If it is difficult to use, it will not be used (simple, huh?) User needs to know: where am I? where have I been? who am I? where can I go from

Navigational Aids: Metaphors

Common ones from office objects books cassette-players film projectors geography maps

Very often they generate terminology and become “slang”

Page 16: Navigation If it is difficult to use, it will not be used (simple, huh?) User needs to know: where am I? where have I been? who am I? where can I go from

Navigational Aids: Histories

Provide information about“where you have been so far”

Combined with navigational structuresprovide a strong navigational tool

Choose what to includesince they grow very fast

Page 17: Navigation If it is difficult to use, it will not be used (simple, huh?) User needs to know: where am I? where have I been? who am I? where can I go from

Navigational Aids: Travel buttons

Home, Next, Previous, Back, Beginning, Quit

Traditionally the only/main navigational aid

Explicitly denote options

Should remain in same relative position

Related buttons should be grouped

Page 18: Navigation If it is difficult to use, it will not be used (simple, huh?) User needs to know: where am I? where have I been? who am I? where can I go from

Navigational Aids:Progress indicators

Very useful when there is a mass to be covered

Thermometers, gauges, clocks, filled bars, ...