Successfully reported this slideshow.

Using Microinteractions to get from Prototype to Product



Upcoming SlideShare
Design in the Post-PC Era
Design in the Post-PC Era
Loading in …3
1 of 26
1 of 26

More Related Content

Related Audiobooks

Free with a 14 day trial from Scribd

See all

Using Microinteractions to get from Prototype to Product

  1. 1. Prototypes generally demonstrate a key feature. But a feature isn’t a product.
  2. 2. The difference between a prototype and a product? All the microinteractions.
  3. 3. dan saffer // @odannyboy #microinteractions using microinteractions to get from prototype to product
  4. 4. microinteractions are single use case pieces of functionality
  5. 5. microinteractions are contained product moments... change a setting sync your data/devices log in see what the current status is viewing a small piece of content error recovery update software/firmware connect to the internet turn a device on/off
  6. 6. Why think about microinteractions at all? Isn’t a Minimum Viable Product enough?
  7. 7. via Stephen Anderson
  8. 8. If you don’t know what happens when someone presses the On button, you don’t have a product yet.
  9. 9. Microinteractions are about conveying the quality of your product.
  10. 10. what quality brings you higher adoption (in some markets) better PR and word-of-mouth funding stronger brand customer loyalty fewer customer service issues/complaints safety
  11. 11. If microinteractions are poor, the main features, no matter how nicely done, are surrounded by pain and frustration.
  12. 12. The difference between a product you love and one you tolerate are often the microinteractions you have with it.
  13. 13. If done well, microinteractions can be signature moments that increase adoption and customer loyalty.
  14. 14. TRIGGER
  15. 15. RULES
  16. 16. FEEDBACK
  17. 17. LOOPS & MODES
  18. 18. The details are the design. Charles Eames
  19. 19. Thank you!