Microinteractions
Synonyms: micro-interactions, micro-animations, UI feedback animations, interaction details, functional animation
Definition
Use cases
- Rage-tapping Pay: The button has no pressed or loading state, so users tap 3 times and get charged 3 times. A classic forum question: “Why do users double-submit forms?”
- The silent save: An autosave editor shows no “Saved” label. Users paste their work into Notes “just in case” and stop trusting the product.
- Animation overload: Every button bounces. It’s fun on day 1, tiring by day 30, and physically uncomfortable for motion-sensitive users.
How it's used in practice
- Write the 4 parts first: List the trigger, rule, feedback, and loop before you animate anything.
- Design every state: Default, hover, pressed, loading, success, error, disabled. Build them as component variants.
- Use real timing: About 100 ms for toggles and checkboxes, 200 to 500 ms for bigger moves. Hand off duration and easing as tokens.
- Respect reduced motion: Swap movement for a fade when the user’s OS setting asks for less motion.
Challenges & limitations
- Lost in handoff: The prototype has motion and the shipped build has a hard cut, because the timing specs never reached the ticket.
- Hard to measure: You can’t A/B test a 150 ms ease-out with 200 users. Most calls rest on usability testing and judgment.
- Performance cost: Heavy animation files drop frames on cheap Android phones. A stuttering animation feels worse than none.
Free resources
- NN/g: Why Microinteractions Are Important for UX — short video on why small UI details shape the experience
- NN/g: Executing UX Animations: Duration and Motion Characteristics — timing ranges, easing, and the 100 ms rule for simple feedback
