Martin Hochenwarter
Why Prototype?
Prototyping Tools
Choosing the right tool
Introduction to
Sketch
InVision
Framer / Origami Studio
Conclusion
Build to
Think
Build to
Show
Build to
Test
Prototypes allow you to ‘think with your hands’
Encounter unconsidered details
Make compromises
Connect with underlying materials
Prototypes communicate concepts to others
Get a shared understanding about the concept
Set the stage for productive collaboration
Show to sell a concept
Prototypes provoke reactions in others
Let others test the prototype
Get feedback on usability
Construct accurate models of the user
Rapid identification of problems
Build to
Think
Build to
Show
Build to
Test
Visions
Paths
Sketches
Systems /
Frameworks
Explore
Refine
Software
... or Pen and Paper
Software
Software
Software
Visions
Paths
Sketches
Systems /
Frameworks
Visions
Paths
Sketches
Systems /
Frameworks
Flexibility
Speed
Fidelity
Fidelity
Fidelity
Fidelity
Flexibility
Flexibility
Flexibility
Speed
Speed
Speed
* Hybrid approach?
Reuse generic components, use sketches for exotic parts
*
Choose between three properties ...
How quickly can an idea be brought to life?
Keep things simple
As little design / interactivity as possible
Don't waste time on bad concepts
by april3rd
How accurately do we reflect final design intent?
What will the final UX be like?
Visual fidelity
Data fidelity
Interactive fidelity
Simple sketches
No Interactivity
Lorem Ipsum
Wireframes / Design
Low Interacvtivity
Static Data
Design
High Interactivity
Dynamic Data
Build upon this prototype over time?
Can elements of the prototype be reused in production?
Choose the right tool and fidelity depending on your requirements
Start simple, explore, refine and iterate often
Reuse as much as possible
The tools change but principles remain the same
Do you use prototypes in your project?
Yes?
What approaches / tools do you use?
How do you like it?
Could it be improved?
No?
Why not?
Would the usage of prototypes improve your project?