We have been shown micro Interactions before and already had a rudimentary understanding of what they are. Now though after reading Dan Saffers book on Micro Interactions I think I have a more in depth grasp on each of the steps involved. Would even go as far as to say I could speak about them quite articulately.

Understanding Triggers, Rules, Feedback and loops and modes Is only the structure of the micro Interaction. What I thought was most valuable from this book was something that resonates throughout UX fundamentals. Understanding the pain points, how the user perceives the interactions (the details) and implementing something that can can solve the issue. Playful Interactions is the name of this module but it’s problem solving in a different format really.

Micro Interactions By Dan Saffer

Well the opening sentence from this book sums up this assignment nicely. ‘It’s the little things that make up the difference between a good digital product sand a great one’.

From his conference he illustrated just how much a small interaction can have such a small impact. The story of the reader losing their images on their apple computer without any notification or warning. I found this shocking to be honest particularly from an apple device; no clear prompts or warnings, not even clear instructions on how to recover the files. This reader did did find the help online from apple and was able to recover the files but all this resulted in was a poor user experience.

So the question was pressed…Are micro interactions details? Damn right: The magic is in the details.

He put these details into a clear concise analogy. Designers love to get the big picture right. It’s a wonderful feeling. No problem is too large. But even if the big picture is done right, unless the details are handled properly, the solution fails: The details are what control the moment to moment experience. It is timely details that lead to seamless interaction with our products. Alternatively, it is the lack of attention to those details that lead to frustration, irritation, and eventually an intense dislike of the product, yes the big picture matters, but so does the detailed picture. It is the attention to detail that creates a smooth feeling of accomplishment. He outlined the steps in great micro interactions. The first in my opinion is probably the most difficult…identifying the situation properly. To identify logical sequences and pain points does require great observational skills. The second is the implementation. There are lots of design issues to consider here…

Triggers, Rules, Feedback, loops and modes

The trigger initiates the micro interaction, the rules that determine how the interaction works, the feedback that illuminates the rules, and loops and modes, the meta rules that effect the micro interactions - are a way to design and dissect micro interactions.

A good example of a trigger would be turning on a ringer on an iPhone, the trigger is user initiated, meaning the user has to do something - in this case, flip a switch - to begin the micro interaction, thus many micro interactions begin with the users need. What the user wants to accomplish, when they want to do it, and how often. This determines the affordance, accessibility and persistence of the trigger. In Dans book I think this is a great example to explain a trigger with a ringer being quite common, designers would be sure this isn't a hidden micro interaction and would be easily accessible within the UI. A lot of triggers need not be user initiated . Increasingly triggers are system initiated when the device or application itself detects that certain conditions have been met and begins a micro interaction. This could be anything from receiving an email, the time of day or even the change of price in a certain stock. One I’m familiar with is the notification of a potential threat or malicious threat found on your system. A trigger that ranks up there with the most important.


Feedback especially with triggers is a place to express the personality of the product. Indeed feedback could be said along with the overall form, to completely define the products personality. It’s not only graphics, sounds and vibrations: it’s also animations. How does a micro interaction appear and disappear? What happen when an item moves? How fast does it go? does the direction it moves matter?

The obvious candidates within systems are error messages and dialog boxes. Each presents some information, thus implying the next step to be performed. Why not make the next step part of the present step?

Great micro interaction design requires understanding the people who use the product. What they are trying to accomplish, and the steps they need to take. It requires understanding of the context of those interactions. It is essential to develop empathy with the user, to develop the users observational skills, and how to instil the knowledge of how to combine different aspects of your product - perhaps the result of different programming teams or even different divisions - into a single smooth interaction.


Loops & Modes. Although undesirable some micro interactions have different modes. A good example would be a weather app which would have a default mode which based on your location would give you the weather but to see the weather in another location the user would have open an overlay displaying another mode. A great example of a loop would be ‘buy another’ after you’ve already purchased an item on E bay or Amazon.


What I took from the philosophy of Dans book was to look as your product as a whole then consider the micro interactions afterwards. If you keep to the structure and test the Micros accordingly you can enhance the user experience, create elegant micro interactions and even possibly create signature moments. The like button on Facebook or you’ve got mail are old examples but are great ones that express the bands identity. That and keep the the mantra ‘Less is more’.