COAP:COAP-2100/Web design: Difference between revisions
Jump to navigation
Jump to search
m (Created page with "== Introduction == Items to be presented and discussed in class ... == Reading == Read each of these texts. total reading should be less than an hour. I am '''not''' requiri...") |
m (→Introduction) |
||
Line 1: | Line 1: | ||
== Introduction == | == Introduction == | ||
Topics presented and discussed in class ... | |||
; Usability | |||
The general principles are: '''efficiency, effectiveness and sastisfaction'''. | |||
These principles can be detailed as: | |||
* easy to learn (task time) | |||
* efficient to use (task time) | |||
* effective to use (errors and task completion) | |||
* provides quick recovery from errors (errors and task completion) | |||
* easy to remember (task time) | |||
* enjoyable to use (subjective user satisfaction) | |||
* visually pleasing (subjective user satisfaction) | |||
[http://www.usability.gov/basics/index.html Usability.gov] presents a similar list: | |||
# Ease of learning - How fast can a user who has never seen the user interface before learn it sufficiently well to accomplish basic tasks? | |||
# Efficiency of use - Once an experienced user has learned to use the system, how fast can he or she accomplish tasks? | |||
# Memorability - If a user has used the system before, can he or she remember enough to use it effectively the next time or does the user have to start over again learning everything? | |||
# Error frequency and severity - How often do users make errors while using the system, how serious are these errors, and how do users recover from these errors? | |||
# Subjective satisfaction - How much does the user like using the system? | |||
Summary: | |||
* '''Basically''', usability testing means giving people tasks to do and observing them | |||
* Only ''user experience'' (satisfaction and related) is measured with questionnaires | |||
We will look at the [http://www.usability.gov/templates/docs/short_test_rep.doc Short (informal) usability test report template (DOC - 216KB)] template from usability.gov: | |||
; Landing page optimization | |||
The five second test according to [http://unbounce.com/landing-page-optimization/the-5-second-rule-best-sites-of-2009-part-1/ Oli Gardner] | |||
# What is it about?: How obvious is the core brand message? | |||
# Do I care?: Am I interested? Does it speak to me? | |||
# Is it trustworthy?: Does the design make me feel comfortable? Do they appear professional? | |||
# How do I participate?: What am I supposed to do first? Is the primary call to action presented in a clear manner? | |||
# Is it newsworthy?: Given today’s social web economy, how likely am I to want to share my experience? Is this facilitated in any way? | |||
; Contents of the landing page | |||
* [http://www.useit.com/alertbox/20020512.html Nielson's list] | |||
; Web site layout navigation principles | |||
([http://webstyleguide.com/wsg3/4-interface-design/3-interface-design.html Lynch and Horton]): | |||
* No dead-end pages | |||
* Direct access | |||
* Simplicity and consistency | |||
* Design integrity and stability | |||
* Feedback and dialog | |||
* Bandwidth and interaction | |||
* Interface design conventions ([http://webstyleguide.com/wsg3/figures/4-interface-design/4-17-700.jpg picture]) | |||
; Wireframing - a first stage in proto-typing | |||
* Drawing a sketch for a "multi-boxed" web page (e.g. a portal). Demo of [https://gomockingbird.com/mockingbird/ Mockingbird] and [http://www.mockflow.com/ Mockflow] | |||
* Using a drawing tool such as Inkscape or a genral-purpose online drawing tool. Demo of [http://inkscape.org/download/ Inkscape] (free drawing tool), [http://www.gliffy.com/ Gliffy] and [https://creately.com/ Creatly]. | |||
* Templating (very short introduction, this is more a self-study object for those who are able to dig into technical documentation and maybe some XML) | |||
== Reading == | == Reading == |
Revision as of 21:46, 1 February 2011
Introduction
Topics presented and discussed in class ...
- Usability
The general principles are: efficiency, effectiveness and sastisfaction.
These principles can be detailed as:
- easy to learn (task time)
- efficient to use (task time)
- effective to use (errors and task completion)
- provides quick recovery from errors (errors and task completion)
- easy to remember (task time)
- enjoyable to use (subjective user satisfaction)
- visually pleasing (subjective user satisfaction)
Usability.gov presents a similar list:
- Ease of learning - How fast can a user who has never seen the user interface before learn it sufficiently well to accomplish basic tasks?
- Efficiency of use - Once an experienced user has learned to use the system, how fast can he or she accomplish tasks?
- Memorability - If a user has used the system before, can he or she remember enough to use it effectively the next time or does the user have to start over again learning everything?
- Error frequency and severity - How often do users make errors while using the system, how serious are these errors, and how do users recover from these errors?
- Subjective satisfaction - How much does the user like using the system?
Summary:
- Basically, usability testing means giving people tasks to do and observing them
- Only user experience (satisfaction and related) is measured with questionnaires
We will look at the Short (informal) usability test report template (DOC - 216KB) template from usability.gov:
- Landing page optimization
The five second test according to Oli Gardner
- What is it about?: How obvious is the core brand message?
- Do I care?: Am I interested? Does it speak to me?
- Is it trustworthy?: Does the design make me feel comfortable? Do they appear professional?
- How do I participate?: What am I supposed to do first? Is the primary call to action presented in a clear manner?
- Is it newsworthy?: Given today’s social web economy, how likely am I to want to share my experience? Is this facilitated in any way?
- Contents of the landing page
- Web site layout navigation principles
- No dead-end pages
- Direct access
- Simplicity and consistency
- Design integrity and stability
- Feedback and dialog
- Bandwidth and interaction
- Interface design conventions (picture)
- Wireframing - a first stage in proto-typing
- Drawing a sketch for a "multi-boxed" web page (e.g. a portal). Demo of Mockingbird and Mockflow
- Using a drawing tool such as Inkscape or a genral-purpose online drawing tool. Demo of Inkscape (free drawing tool), Gliffy and Creatly.
- Templating (very short introduction, this is more a self-study object for those who are able to dig into technical documentation and maybe some XML)
Reading
Read each of these texts. total reading should be less than an hour. I am not requiring recall of details, but ought to be able to locate information in these texts ....
- Top Ten Guidelines for Homepage Usability (Jakob Nielsen)
- The Elements of User Experience (the complicated picture) by Jess James Garet
- Interface Design (part of Lynch and Norton's Web Style Guide)
- Usability testing on 10 cents a day by Steve Krug
- Top 10 best designed web sites by Scratch (this is just one of many such lists, look at 1-2 examples)
- The 5 Second Rule: Critiquing the Best Websites of 2009 – Part 1 (demonstrates a method to judge initial user experience/usability)
Prototyping and wireframing (tested in exam !)
- Paper Prototyping by Shwan Medero, A List Apart, 2007.
- Website wireframe (Wikipedia)