Marcus Andrey Study
Ler em português Library

Framework · Motion & interaction · 4 min read

Microinteraction model

Dan Saffer's four parts of a microinteraction (trigger, rules, feedback, loops and modes), used as a checklist so a small moment gets designed, specced and tested instead of left to the animation.

TTrigger

What starts it: a person, or the system.

A tap, a key, 08:00
RRules

What happens, what can't, and what if it fails.

Write them before animating
FFeedback

How it shows the rules ran, in more than one channel.

Motion, colour, words
LLoops, modes

What happens later, and in another state.

Resets after 2 seconds

Trigger → Rules → Feedback → Loops and modes, plus a reduced-motion row and a screen-reader row

Dan Saffer's four parts of a microinteraction: the rules are invisible, so they are the part most often left undesigned.

Use it when

  • A small control (a toggle, a like, a copy button, a save) works in the prototype but feels wrong, and nobody can say why.
  • You hand a microinteraction to a developer and want it rebuilt the same way, not reinterpreted.
  • You review a screen and want a quick way to find what the designer skipped.

How to use it

  1. Name the one job. Write one sentence: what this moment does for the person. If it has two jobs, it's two microinteractions, or a flow. Output: one sentence, for example "Copy the link to the clipboard".
  2. Write the trigger. Say what starts it: a person (tap, key, voice) or the system (a time, a new message). If the trigger is hidden, such as a long press or a swipe, add a visible way to do the same thing. Output: the trigger, and its visible alternative if it has one.
  3. Write the rules. In plain sentences: what happens, what happens on a double press, what can't happen, what happens when it fails. Output: three to six rule sentences.
  4. Design the feedback in more than one channel. Pair motion with colour, words or an icon change, so the answer still arrives with reduced motion, a glance away or a screen reader. Start the response within about 0.1 second of the trigger, and keep it short on things people do often. Output: the feedback per channel, with a duration for the motion.
  5. Decide loops and modes. Loops are time: does it reset, expire, remember? Modes are a second set of rules in another state. Keep modes rare: a control that quietly changes meaning causes errors. Output: what happens later, and any mode, with how the person sees it.
  6. Add the two rows most specs forget. What it does with reduced motion, and what a screen reader hears when the change doesn't move focus. Output: a one-page spec a developer can build and QA can test.

Worked example

A task app for small teams has a "Copy link" button on every task. People say it "sometimes doesn't work". Written down with the model:

Part Decision
Trigger Tap or click the button, or Ctrl/Cmd + C when the task is focused
Rules Copies the task link. Pressing twice copies twice; nothing breaks. If the clipboard is blocked, it says so and shows the link to copy by hand
Feedback The icon turns into a check in 150 ms, the label changes to "Copied", a screen reader hears "Link copied"
Loops and modes After 2 seconds it goes back to "Copy link". No modes
Reduced motion The icon swaps without the scale; label and announcement stay

The "doesn't work" turned out to be a rule: when the clipboard was blocked, the old button did nothing at all. No animation would have fixed it.

Watch out for

  • Designing the animation and skipping the rules. The rules are invisible, so they get forgotten, and they cause most of the problems.
  • Feedback that is only motion. It disappears with reduced motion, a glance away or a screen reader. Always add a second channel.
  • A hidden trigger with no visible twin. Most people never find long presses and swipes. Use them as shortcuts, not as the only way.
  • A celebration on something people do twenty times a day. Keep frequent feedback brief; save the flourish for rare moments, if at all.

Template

Copy this into the ticket or the design file, one per microinteraction.

Microinteraction: ...
Job (one sentence): ...

Trigger: ...
  Visible alternative (if the trigger is hidden): ...
Rules:
  - What happens: ...
  - Pressed twice: ...
  - What can't happen: ...
  - If it fails: ...
Feedback:
  - Motion: ... (duration ... ms, starts within 0.1 s)
  - Colour / icon: ...
  - Words: ...
Loops: ... (reset after ..., remembers ...)
Modes: none / ...
Reduced motion: ...
Screen reader hears: ...
Source
Dan Saffer, Microinteractions (O'Reilly, 2013): triggers, rules, feedback, loops and modes. Response within 0.1 second: Aurora Harley (NN/g, 2014). Status messages: W3C, WCAG 2.2 success criterion 4.1.3

"See on Amazon" links are affiliate links. As an Amazon Associate I earn from qualifying purchases, at no extra cost to you.

Saved only on this device.

↑ ↓ to move · Enter to open · Esc to close