Motion and Interaction · Step 3 · 6 min read
Anatomy of a microinteraction
A microinteraction is one small moment with one job: mute, like, save, switch on. Dan Saffer's four parts (trigger, rules, feedback, loops and modes) turn it from a nice animation into a design you can spec, test and hand off.
A microinteraction is a tiny conversation: you do one thing, the interface answers. Muting a chat, liking a photo, turning on dark mode. Each one is small, and people do them hundreds of times. Most teams design the look of the switch and leave the rest to chance: what starts it, what it does, how it answers, what happens later. Name those four parts and the moment stops being decoration and becomes something you can design.
What you'll be able to do after reading:
- Name the four parts of a microinteraction: trigger, rules, feedback, loops and modes
- Spot what's missing in a microinteraction that "feels off"
- Write a one-page spec for one
- Decide how much motion its feedback needs, and what it says without motion
1. One toggle, four parts
Try it: click, tap, or Tab to it and press Space.
- 1TriggerThe switch and its whole label. A tap, a click or the Space key starts it.
- 2RulesOne press flips the state. On means no sounds until 08:00 tomorrow, then it turns itself off.
- 3FeedbackThe knob slides in 200 ms, the track fills with colour, and the line under the label says what changed.
- 4Loops and modesThe loop: at 08:00 it switches off by itself. No modes: one switch, one job.
Try the switch. It looks like one thing, but there are four decisions in it. Dan Saffer named them in his book Microinteractions (O'Reilly, 2013), which explores "a microinteraction's structure: triggers, rules, feedback, modes, and loops" (Google Books, the publisher's description):
- Trigger: what starts it. A person (a tap, a key, a voice command) or the system (a time, a new message, low battery).
- Rules: what happens, and what can't. The rules are invisible; people learn them only through the feedback.
- Feedback: how the interface shows that the rules ran. Motion, colour, words, sound, a vibration.
- Loops and modes: what happens over time (it switches itself off at 08:00, it remembers your choice) and whether it behaves differently in another state.
NN/g puts the core of it in one line: microinteractions are "trigger-feedback pairs", and the feedback is a "narrowly targeted response to the trigger", usually placed close to it (NN/g, Microinteractions in User Experience, 2018). A static element isn't one, because nothing triggers it; a whole flow isn't one either, because it has many jobs.
2. The trigger: make it findable
A trigger is only useful if people find it. A visible control (a switch, a button, a heart) is a trigger that explains itself. A hidden one (a long press, a swipe, a shake) is a shortcut that most people will never discover, which is why the next lessons always pair it with a visible way.
System triggers need the same care. A notification that arrives while you're typing, or a "Saved" that appears on its own, is a microinteraction too. Ask: will the person notice it, and will they understand what caused it?
3. Rules: decide them before you animate
The rules are where most "it feels off" problems come from, and no easing curve can fix them. For the toggle above:
- What does "on" mean, exactly? (No sounds until 08:00 tomorrow.)
- What happens if the person presses twice quickly? (It flips twice. Nothing breaks.)
- What can't happen? (It can't be on and show "sounds on" at the same time.)
Write the rules in plain sentences first. If you can't, the design isn't ready for motion yet.
4. Feedback: say it three ways
Feedback is where motion lives, and where it's easiest to overdo. The toggle's knob slides in 200 ms: short enough to feel like a direct answer to the press, long enough to show the knob travelled from one side to the other. But the slide is not alone. The track fills with colour and the line under the label changes to "On until 08:00 tomorrow".
That redundancy is the point. Motion is one channel; colour and words are others. If the motion is reduced (see Vestibular disorders and reduced motion), if someone looks away, or if a screen reader is speaking, the news still arrives. Apple's guidelines say the same about motion in general: don't use it as the only way to communicate important information (Apple HIG, Motion).
Two more rules for feedback:
- Start it fast. For people to feel that their action caused the change, the response should begin within 0.1 seconds (NN/g, Animation for Attention and Comprehension, 2014).
- Keep it in proportion. Apple advises avoiding extra motion on interactions that happen often, and keeping feedback animations brief and precise (Apple HIG, Motion). A toggle used ten times a day deserves 200 ms, not a celebration.
5. Loops and modes: what happens later
Loops are time. The toggle switches itself off at 08:00; a "Copied" label goes back to "Copy" after two seconds; a like button remembers you liked. Modes are a second set of rules: the same control doing something else in another state. Keep them rare: every mode is something people have to notice and remember, and a control that quietly changes meaning is a classic source of errors. One switch, one job.
6. Write it down: a one-page spec
| Part | What we decided | Why |
|---|---|---|
| Trigger | The "Add to basket" button on a product page. Mouse, touch, Enter or Space. | A visible button, not a gesture: everyone can find it and press it. |
| Rules | Adds one item. A second press adds another. If the item is out of stock, the button is disabled and says so. | People press twice when nothing seems to happen; the rule has to be safe either way. |
| Feedback | The button shows its pressed state at once. Within 1 second the basket count goes up by one with a short 200 ms bump, and the button reads "Added". | Under 0.1 s the press feels instant; the count shows where the item went. |
| Loops and modes | After 2 seconds the label goes back to "Add to basket". No modes. | The button is ready for the next press without a page reload. |
| Reduced motion | No bump: the count changes and its badge colour flashes once. | The news is in the number and the words, not in the movement. |
| Screen readers | "Added to basket, 3 items" is announced as a status message. | WCAG 4.1.3: a change that doesn't move focus still has to be heard. |
A microinteraction is small enough to spec on one page, and it's worth it: a developer can build it, QA can test it, and the next designer won't redesign it by accident. Add the two rows most specs forget: what it does with reduced motion, and what a screen reader hears. A change that doesn't move focus must still be announced (W3C, Understanding 4.1.3 Status Messages).
7. Common mistakes
- Designing the animation and skipping the rules.
- Feedback that is only motion, so it disappears with reduced motion or a glance away.
- A hidden trigger (long press, swipe) with no visible way to do the same thing.
- The same 600 ms flourish on something people do twenty times a day.
- Modes nobody asked for: a control that changes meaning without saying so.
8. Vocabulary
| Term | Meaning |
|---|---|
| Microinteraction | One small moment with one job: a trigger and the interface's answer to it |
| Trigger | What starts it: a person's action or a system condition |
| Rules | What happens, in what order, and what can't happen |
| Feedback | How the interface shows that the rules ran: motion, colour, words, sound, touch |
| Loop | What happens over time or on the next use |
| Mode | A second set of rules for the same control |
9. Try it (no tools needed)
- Pick one microinteraction in an app you use every day: a like, a mute, a "mark as read".
- Write its four parts in four lines.
- Now turn off the motion in your head: what still tells you it worked?
Reflection questions: Which of the four parts did you have to guess? If a developer rebuilt it from your four lines, would it come out the same?
10. If you already practise
- Keep a spec template with the four parts plus "reduced motion" and "screen reader", and use it for every new control.
- In critique, ask "what are the rules?" before anyone comments on the easing.
- Collect your product's microinteractions in one place; repeated ones are candidates for components and Motion tokens.
Checklist
Learn more
- Alita Kendrick, Microinteractions in User Experience (NN/g, 2018)
- Aurora Harley, Animation for Attention and Comprehension (NN/g, 2014)
- Apple, Human Interface Guidelines: Motion · Feedback
- W3C, Understanding 4.1.3 Status Messages
Books, courses and videos to go deeper
- MicrointeractionsDan SafferBook · O'Reilly, 2013 (Amazon)
- Designing Interface AnimationVal HeadBook · Rosenfeld Media, 2016 (Amazon)
Book links go to Amazon. As an Amazon Associate I earn from qualifying purchases, at no extra cost to you.
Related
Affordances, signifiers and feedback · Interface states: empty, loading, error, success · Interactive states: hover, press, focus · Prototype a microinteraction in Figma · Duration: how long is right · Microinteraction model