Embed Size (px)
Citation preview
Prototyping for Richer User ExperiencesChris GriffithQualcomm, Inc.User Experience Group
About Me
What is a prototype?
…incomplete versions of the software program being developed. A prototype typically implements only a small subset of the features of the eventual program, and the implementation may be completely different from that of the eventual product.
(http://en.wikipedia.org/wiki/Software_prototyping)
Why prototype?
Proof of Concept
Design Validation
Management By-in
Reduce Misinterpretations
Source: http://www.whattofix.com/blog/archives/2008/05/peace_for_pachy.php
Save Time and $$$
“We don’t have the time to prototype?”
“We can’t afford to prototype. We don’t have the budget.”
SharedCommunications
User Testing
Power ofShow and Tell
Guidelines for Prototyping
Short Timeframe
Build only what you need
Don’t be afraid to throw it out!
Types of Prototyping
Low Fidelity
Medium Fidelity
High Fidelity
Low Fidelity Prototyping
Quick to develop
Allows for explorations of ideas
Can be more difficult to conduct user studies
Zero coding!
Paper Prototyping
Source: http://usereccentric.com/entries/000333.html
Paper Prototyping - sketching
Tools
Resources
Medium Fidelity Prototyping
More “real” user experience
Longer design time
Longer development time
Some level of programming
“Golden Path” / Slideshow
Medium Fidelity
Tools
High Fidelity Prototyping
Closer to reality
Greater design requirements
More development time
Can serve as a reference platform for other groups (Engineering, QA, Marketing)
High Fidelity
Tools
Demo
Testing
Source http://usability.wikimedia.org/wiki/File:Research-Photo-LabTesting.jpg
Prototyping Pitfalls
Fidelity Trap
“Looks done to me, ship it”
Prototyping: A Practitioner's Guide
Resources
Keys to Successful Prototyping
Short development time
Throw-away code (mostly)
Fake it (when you can)
Q&A
Contact me:
Twitter: @chrisgriffith
Blog: http://chrisgriffith.wordpress.com/
Thanks!
