Rules of UI prototyping
Download as PPT, PDF3 likes858 views
This document provides rules for effective UI prototyping, including keeping iterations frequent but not too small, focusing on layouts and behaviors in each cycle, using real sample data and contexts, validating prototypes early and often, keeping prototypes low fidelity, clearly communicating intentions, and ensuring prototypes support business objectives.
![Rules of UI Prototyping Alex Kouznetsov, PhD [email_address]](https://image.slidesharecdn.com/rulesofprototyping-110426193533-phpapp02/85/Rules-of-UI-prototyping-1-320.jpg)
![Thanks! [email_address] 2010, Alex Kouznetsov](https://image.slidesharecdn.com/rulesofprototyping-110426193533-phpapp02/85/Rules-of-UI-prototyping-12-320.jpg)
Rules of UI prototyping
- 1. Rules of UI Prototyping Alex Kouznetsov, PhD [email_address]
- 2. Up to 5 changes per iteration Iterations are not too small and not too slow
- 3. 1-2 iterations a day Keep the pace and get feedback
- 4. Go from A to Z in each prototyping cycle Go wide before going deep. Don't get stuck in deep prototyping of one piece of the app. Make a full circle and return for deeper iteration.
- 5. Focus on layouts and behaviors Layouts - find and navigate Behaviors - interaction
- 6. Use samples of real context (instead of generic label) The prototype of a "dog" should "look and walk like a dog"
- 7. Use samples of real data There is always something to learn from real data
- 8. Early validation IN and OUT Within the team, across teams and with customers
- 9. Lo-Fi is OK Don't refine design in prototyping. We don't need high quality design for prototyping
- 10. Clear communication That's what prototype is good for (plus discovery). Show, explain intention and get a feedback.
- 11. Support business objectives This is the bottom line. Always keep the business in mind (customers)
- 12. Thanks! [email_address] 2010, Alex Kouznetsov