Prototyping for Richer User Experiences Chris Griffith Qualcomm, 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. (
Why prototype?
Proof of Concept
Design Validation
Management By-in
Reduce Misinterpretations
Source:
Save Time and $$$ “We don’t have the time to prototype?” “We can’t afford to prototype. We don’t have the budget.”
Shared Communications
User Testing
Power of Show 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:
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
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: Blog:
Thanks!