×
Namespaces

Variants
Actions
(Difference between revisions)

Series 40 UI design usability testing webinar - companion article

From Nokia Developer Wiki
Jump to: navigation, search
Krebbix (Talk | contribs)
(Krebbix -)
 
Krebbix (Talk | contribs)
(Krebbix -)
Line 1: Line 1:
[[Category:Draft]]
+
[[Category:Draft]][[Category:Testing]][[Category:Usability]][[Category:User Experience]][[Category:GUI testing]][[Category:Training]][[Category:Series 40]]
''Delete instructional text in italic''
+
  
{{Abstract|This article explains how to ... }} ''Replace the abstract text with a short paragraph (or sentence) describing what the topic covers.''
+
{{Abstract|This article is companion for the ''Debug your design for Series 40 Full Touch'' webinars held in December 2012. It covers both sessions: 11<sup>th</sup>  and 12<sup>th</sup> December 2012.}}
  
''Enter article metadata as described below. Note that this template can be placed anywhere in the article. Do not remove parameters that you do not use''
 
 
{{ArticleMetaData <!-- v1.2 -->
 
{{ArticleMetaData <!-- v1.2 -->
 
|sourcecode= <!-- Link to example source code e.g. [[Media:The Code Example ZIP.zip]] -->
 
|sourcecode= <!-- Link to example source code e.g. [[Media:The Code Example ZIP.zip]] -->
Line 12: Line 10:
 
|platform= <!-- Compatible platforms - e.g. Symbian^1 and later, Qt 4.6 and later -->
 
|platform= <!-- Compatible platforms - e.g. Symbian^1 and later, Qt 4.6 and later -->
 
|devicecompatability= <!-- Compatible devices e.g.: All* (must have internal GPS) -->
 
|devicecompatability= <!-- Compatible devices e.g.: All* (must have internal GPS) -->
|dependencies= <!-- Any other/external dependencies e.g.: Google Maps Api v1.0 -->  
+
|dependencies= <!-- Any other/external dependencies e.g.: Google Maps Api v1.0 -->
|signing=<!-- Signing requirements - empty or one of: Self-Signed, DevCert, Manufacturer -->
+
|signing= <!-- Signing requirements - empty or one of: Self-Signed, DevCert, Manufacturer -->
 
|capabilities= <!-- Capabilities required by the article/code example (e.g. Location, NetworkServices. -->
 
|capabilities= <!-- Capabilities required by the article/code example (e.g. Location, NetworkServices. -->
 
|keywords= <!-- APIs, classes and methods (e.g. QSystemScreenSaver, QList, CBase -->
 
|keywords= <!-- APIs, classes and methods (e.g. QSystemScreenSaver, QList, CBase -->
 
|language= <!-- Language category code for non-English topics - e.g. Lang-Chinese -->
 
|language= <!-- Language category code for non-English topics - e.g. Lang-Chinese -->
 
|translated-by= <!-- [[User:XXXX]] -->
 
|translated-by= <!-- [[User:XXXX]] -->
|translated-from-title= <!-- Title only -->  
+
|translated-from-title= <!-- Title only -->
 
|translated-from-id= <!-- Id of translated revision -->
 
|translated-from-id= <!-- Id of translated revision -->
|review-by=<!-- After re-review: [[User:username]] -->
+
|review-by= <!-- After re-review: [[User:username]] -->
 
|review-timestamp= <!-- After re-review: YYYYMMDD -->
 
|review-timestamp= <!-- After re-review: YYYYMMDD -->
 
|update-by= <!-- After significant update: [[User:username]]-->
 
|update-by= <!-- After significant update: [[User:username]]-->
 
|update-timestamp= <!-- After significant update: YYYYMMDD -->
 
|update-timestamp= <!-- After significant update: YYYYMMDD -->
|creationdate= <!-- Format YYYYMMDD -->
+
|creationdate= 20121210
|author= <!-- Display as link [[User:username]] -->
+
|author= [[User:Krebbix]]
 
}}
 
}}
 +
  
 
== Introduction ==
 
== Introduction ==
  
 +
You know it’s important to test your app before you publish it, but if you’re testing only your code, you’re testing only part of your app. It’s important to find bugs in your design as well. Otherwise, the app may behave exactly the way your code intends, but users may still find it frustrating and give it low ratings in Nokia Store. Join UX expert Jan Krebber of Digia as he presents simple methods to find UX bugs and shows you how to correct them. These techniques can help you increase your app quality whether you work with a large organization or completely on your own. As usual for Nokia Developer UX webinars, the presentation will feature exercises that will receive follow-up treatment in this Nokia Developer Wiki article.
 +
 +
The webinar and the wiki article are a great starting point if you’re not a UI design expert. Check out [https://www.developer.nokia.com/Resources/Library/Full_Touch/#!index.html Series 40 UI design library] for more advanced information and resources.
 +
 +
This wiki page is the "companion" to the webinar. It includes:
 +
* Webinar exercises and proposals for how to solve them (will be added after the second webinar session).
 +
* Checklist example from the webinar
 +
* Time plan example from the webinar
 +
* Open issues from Q/A
 +
* Further links and references
 +
* Slide deck link will be added
 +
* Recording link will be added
 +
* [http://www.developer.nokia.com/Resources/Multimedia/Webinars.xhtml Webinar announcement]
 +
 +
==  Webinar problems ==
 +
 +
This section contains problems raised in the webinar exercises.
 +
 +
# Watch the videos.
 +
## What went wrong?
 +
## How do you fix it?
 +
# In which case is it enough to have only 2-3 participants? Why?
 +
# You are not sure what the participant is thinking. What do you say?
 +
# The participant mentions that she is not giving you what you expect from her. What do you say?
 +
# The participant thinks she is doing everything wrong. What do you say to her?
 +
# Why not giving all the tasks on paper to the participant?
 +
# How would you classify the errors you find. Which errors do you fix first?
  
 +
== Checklist example ==
 +
* Get participants (for 28.11.)
 +
* Make schedule
 +
* Get helper to catch the next participant
 +
* Task list & scenarios on paper
 +
* Prototype for all test cases
 +
* Pencil, eraser, paper, scissors, post-its
 +
* Rooms
 +
* Refreshments
 +
* Rewards
 +
* Agreements printed
 +
* Task list & Scenarios on index cards
 +
* Call participants day before and remind (27.11.)
 +
* Run pilot
  
== Summary ==
+
== Time plan example ==
 +
{|
 +
|-
 +
! Minutes !! Tasks
 +
|-
 +
| 00 || Welcome
 +
|-
 +
| 01 || Introduction<br />
 +
* My name is...<br />
 +
* The project is about booking tickets from your mobile phone for 1st and second 2nd league soccer events
 +
|-
 +
| 02 || Read and sign the agreement about the test and NDA is necessary
 +
|-
 +
| 05 || Warm-up questions <br />
 +
* What are you doing for living? <br />
 +
* What are your hobbies? <br />
 +
* How old are you? <br />
 +
* What is your current mobile phone? <br />
 +
* Which phones did you use before that? <br />
 +
* Have you ever bought any goods (real hardware) or event tickets from your mobile phone?
 +
|-
 +
| 10 || Tasks <br />
 +
# Give story 1 (start).
 +
# Book 2 tickets for the game "FC Dudes vs. Dudes United" in March.
 +
# Give story 2 (more info).
 +
# Find information about the event place.
 +
# How do you get there?
 +
# Find more about FC Dudes team.
 +
# How well performed Dudes United in comparison to FC Dudes this year?
 +
# Give story 3 (you go there).
 +
# Drive to the event place.
 +
# Show the e-tickets at the entrance
 +
# Find your location in the stadium
 +
|-
 +
| 40 || Closure <br />
 +
* Open issues <br />
 +
** What was unclear to me?
 +
** Any task which should be done again?
 +
** Any new task I would like to see performed?
 +
* Any questions from the participant?
 +
* I wrap up
 +
** What went well 1-2-3
 +
** What needs improvement so that it becomes easier for the participant 1-2-3
 +
* Give reward
 +
* Thank you & Good bye
 +
|-
 +
| 50 || Transission <br />
 +
* Take additional notes
 +
* Reset prototype
 +
* Refill coffee
 +
* Toilet break
  
 
''Remove Category:Draft when the page is complete or near complete''
 
  
 +
== Open issues from Q/A ==
 +
-
  
''The "platform categories" will be displayed here in '''preview''' only - Copy paste relevant categories into text here''
+
== Further links and references ==
  
{{VersionHint|Versions will be visible from this template when viewed in preview. You can delete this or leave it in the page as it is not displayed in final version}}
+
* [http://www.developer.nokia.com/Resources/Library/Full_Touch/ UI guidelines for Series 40 full-touch]
 +
* [https://projects.developer.nokia.com/s40uivisualisation UI components' demo app]
 +
* [http://www.youtube.com/watch?v=QckIzHC99Xc&feature=player_embedded Test example video by Steve Krug]
 +
* [http://www.useit.com  Jacob Nielsen’s blog]
  
''Add categories below using category selector.''
+
* [[Rocket Surgery Made Easy: The Do-it-yourself Guide to Finding and Fixing Usability Problems (Book) |Rocket Surgery Made Easy: The Do-it-yourself Guide to Finding and Fixing Usability Problems]]. Steve Krug (2009). ISBN-13: 978-0321657299
 +
* [[Paper Prototyping: The Fast and Easy Way to Design and Refine User Interfaces (Book) |Paper Prototyping: The Fast and Easy Way to Design and Refine User Interfaces]]. Carolyn Snyder (2003). ISBN-13: 978-1558608702
 +
* [[Handbook of Usability Testing: How to Plan, Design, and Conduct Effective Tests (Book) |Handbook of Usability Testing: How to Plan, Design, and Conduct Effective Tests.]]. Jeffrey Rubin and Dana Chisnell (2008). ISBN-13: 978-0470185483

Revision as of 17:41, 10 December 2012


This article is companion for the Debug your design for Series 40 Full Touch webinars held in December 2012. It covers both sessions: 11th and 12th December 2012.

Article Metadata
CompatibilityArticle
Created: Krebbix (10 Dec 2012)
Last edited: Krebbix (10 Dec 2012)


Contents

Introduction

You know it’s important to test your app before you publish it, but if you’re testing only your code, you’re testing only part of your app. It’s important to find bugs in your design as well. Otherwise, the app may behave exactly the way your code intends, but users may still find it frustrating and give it low ratings in Nokia Store. Join UX expert Jan Krebber of Digia as he presents simple methods to find UX bugs and shows you how to correct them. These techniques can help you increase your app quality whether you work with a large organization or completely on your own. As usual for Nokia Developer UX webinars, the presentation will feature exercises that will receive follow-up treatment in this Nokia Developer Wiki article.

The webinar and the wiki article are a great starting point if you’re not a UI design expert. Check out Series 40 UI design library for more advanced information and resources.

This wiki page is the "companion" to the webinar. It includes:

  • Webinar exercises and proposals for how to solve them (will be added after the second webinar session).
  • Checklist example from the webinar
  • Time plan example from the webinar
  • Open issues from Q/A
  • Further links and references
  • Slide deck link will be added
  • Recording link will be added
  • Webinar announcement

Webinar problems

This section contains problems raised in the webinar exercises.

  1. Watch the videos.
    1. What went wrong?
    2. How do you fix it?
  2. In which case is it enough to have only 2-3 participants? Why?
  3. You are not sure what the participant is thinking. What do you say?
  4. The participant mentions that she is not giving you what you expect from her. What do you say?
  5. The participant thinks she is doing everything wrong. What do you say to her?
  6. Why not giving all the tasks on paper to the participant?
  7. How would you classify the errors you find. Which errors do you fix first?

Checklist example

  • Get participants (for 28.11.)
  • Make schedule
  • Get helper to catch the next participant
  • Task list & scenarios on paper
  • Prototype for all test cases
  • Pencil, eraser, paper, scissors, post-its
  • Rooms
  • Refreshments
  • Rewards
  • Agreements printed
  • Task list & Scenarios on index cards
  • Call participants day before and remind (27.11.)
  • Run pilot

Time plan example

Minutes Tasks
00 Welcome
01 Introduction
  • My name is...
  • The project is about booking tickets from your mobile phone for 1st and second 2nd league soccer events
02 Read and sign the agreement about the test and NDA is necessary
05 Warm-up questions
  • What are you doing for living?
  • What are your hobbies?
  • How old are you?
  • What is your current mobile phone?
  • Which phones did you use before that?
  • Have you ever bought any goods (real hardware) or event tickets from your mobile phone?
10 Tasks
  1. Give story 1 (start).
  2. Book 2 tickets for the game "FC Dudes vs. Dudes United" in March.
  3. Give story 2 (more info).
  4. Find information about the event place.
  5. How do you get there?
  6. Find more about FC Dudes team.
  7. How well performed Dudes United in comparison to FC Dudes this year?
  8. Give story 3 (you go there).
  9. Drive to the event place.
  10. Show the e-tickets at the entrance
  11. Find your location in the stadium
40 Closure
  • Open issues
    • What was unclear to me?
    • Any task which should be done again?
    • Any new task I would like to see performed?
  • Any questions from the participant?
  • I wrap up
    • What went well 1-2-3
    • What needs improvement so that it becomes easier for the participant 1-2-3
  • Give reward
  • Thank you & Good bye
50 Transission
  • Take additional notes
  • Reset prototype
  • Refill coffee
  • Toilet break


Open issues from Q/A

-

Further links and references

413 page views in the last 30 days.
×