Prototypes generally demonstrate a key feature. But a feature isn’t a product.

The difference between a prototype and a product? All the microinteractions.

dan saffer // @odannyboy#microinteractions

using microinteractions to get from prototype to product

microinteractions are single use case pieces of functionality

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

Why think about microinteractions at all? Isn’t a Minimum Viable Product enough?

via Stephen Anderson

If you don’t know what happens when someone presses the On button, you don’t have a product yet.

Microinteractions are about conveying the quality of your product.

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

If microinteractions are poor, the main features, no matter how nicely done, are surrounded by pain and frustration.

The difference between a product you love and one you tolerate are often the microinteractions you have with it.

If done well, microinteractions can be signature moments that increase adoption and customer loyalty.

TRIGGER

RULES

FEEDBACK

LOOPS & MODES

The details are the design.Charles Eames

Thank you!http://microinteractions.com