A button that doesn't react to a tap makes people tap again. That second tap is how you get duplicate orders and forms sent twice, along with a small loss of trust that's hard to measure and easy to feel.
Micro-interactions are the small responses an interface gives to each action. Most people never notice them when they work, and they notice right away when they're missing.
What a micro-interaction is
Dan Saffer's book Microinteractions describes them in four parts: a trigger that starts them, rules that decide what happens, feedback that shows it, and loops and modes that cover what happens over time. A like button, a toggle, a pull to refresh and a password strength meter all follow that pattern.
The part most products get wrong is feedback. The rule runs, but the person can't see that anything happened.
Every action needs an answer
When someone presses something, the interface should show that it heard the press, that it's working and that it finished. Try both buttons: the first one gives no feedback, the second shows each step.
The states of a button
A well-built button has more states than its default look. It needs a hover state on desktop, a pressed state, a loading state that blocks repeated taps, a success state and a clear error state. Designing them together keeps the button readable in every moment of the flow.
Timing matters as much as motion
Jakob Nielsen's response-time limits are still a good guide. About 0.1 seconds feels instant, around 1 second keeps the person's flow even if they notice the delay, and around 10 seconds is where attention starts to drift. So the pressed state should appear immediately, and anything that takes longer than a second needs a visible loading state.
Motion that explains
Good motion shows where something came from or what changed. In the brand kit we built for Simply Andy, changing a color in the signature generator updates the preview at once, so Andreina sees the result before she copies it into Gmail. Long decorative animations in the middle of a task get in the way, so we save those for moments like a first launch.
Respect reduced motion
Some people turn on reduced motion in their system settings because animation makes them dizzy or distracts them. Browsers expose that choice through the prefers-reduced-motion media query. Every animation on this site checks it and falls back to a simple fade or no motion at all.
