Series 40 UI design usability testing webinar - companion article
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.
- Series 40 UI design usabillity testing webinar - companion article
- Series 40 UI concept design webinar – companion article
- Series 40 UI game design tips webinar – companion article
- Series 40 UI design port from Android webinar - companion article
- Series 40 UX checklist webinar - companion article
- Series 40 UI design for monetization enablers webinar - companion article
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
This section contains problems raised in the webinar exercises.
- Watch the videos. (Videos are pending.)
- What went wrong?
- How do you fix it?
- When are 2-3 participants sufficient for usability testing? Why?
- You are not sure what a participant is thinking. What do you say?
- A participant mentions that she is not giving you what you expect from her. What do you say?
- A participant thinks she is doing everything wrong. What do you say to her?
- Why not give the participant all the tasks on paper?
- How would you classify the errors you find. Which errors do you fix first?
- Get participants (for 28.11.)
- Make schedule
- Get helper to bring the next participant
- Task list & scenarios on paper
- Prototype for all test cases
- Pencil, eraser, paper, scissors, post-its
- Agreements printed
- Task list & scenarios on index cards
- Call participants day before and remind (27.11.)
- Run pilot
Time plan example
|02||Read and sign the agreement about the test and NDA is necessary|
|05|| Warm-up questions |
|10|| Tasks |
|40|| Closure |
|50|| Transition |
Open issues from Q/A
- UI guidelines for Series 40 full-touch
- UI components' demo app
- Test example video by Steve Krug
- Jacob Nielsen’s blog
- 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. Carolyn Snyder (2003). ISBN-13: 978-1558608702
- Handbook of Usability Testing: How to Plan, Design, and Conduct Effective Tests. Jeffrey Rubin and Dana Chisnell (2008). ISBN-13: 978-0470185483