prototype

prototype

1. Why?

   • saving time
   • save the sunk cost
   • make sure you solve the problem
   • help you make decisions
   • acquire knowledge
   • There is no adjustment to be made to the Agile or Waterfall processes to accommodate UX and iterative design.

2. an example:order a pizza

   • Will residents accidentally order pizza?
   • What feedback do residents need that their pizza is on the way?
   • Would residents feel safe ordering pizza from their watch?

3. necessity

   • whether the cost of just implementing the solution is less than prototyping
   • learning from prototype
   • reducing the cost of prototyping.

4. genres of prototypes

   • sketch
     • low-fidelity prototype
     • faster than in any other media
     • useful at the beginning of a design process.
   • bodystorming
     • fast
     • lowest-fidelity
   • Wizard of Oz prototyping
     • for complex, intelligent functionality
     • example: driverless car
   • higher fidelity prototyping tools
     • Figma, InVision, Adobe XD, and Sketch
     • mimic a final product without having to build a final product
     • realistic (faster) system response during the test.
     • can test workflow, specific UI components (e.g. mega menus, accordions), graphical elements
     • frees the designer to focus on observing the test
     • ess likely to be affected by human error
   • Testable Prototype
     • Single page vs. multipage
     • Realistic and detailed vs. hand-sketched
     • Interactive (clickable) vs. static

5. purpose

   • gained the knowledge from making and testing it