Delight is anticipation, reliability, and care. Animation can support those qualities. Animation is not the definition of them.
Principles
- Give people what they need before they know to ask.
- Arrive early with useful defaults and prefilled context.
- Show care in the smallest details.
- Make the product feel attentive to the person using it.
- Work as expected every time.
- Meet the expected path, then offer the extra mile.
- Prefer tiny details with outsized clarity over spectacle.
- Treat delight as icing, not the cake.
- Stay between excess and restriction.
- Leave no important question unanswered in the journey.
Defaults
- Identify the user need before adding motion; infer it from the task and ask only if the missing context changes the design.
- Invest first in reliability, latency, empty states, and clarity.
- Use motion to explain cause and effect, not to decorate.
- Remove novelty that competes with the task.
Prefer / Reject
| Prefer | Reject |
|---|---|
| Anticipatory defaults | Confetti on every success |
| Reliable interactions | Delight that fails under slow networks |
| Quiet craft details | "Make it pop" with no problem statement |
| One meaningful moment | Many competing flourishes |
Review checklist
- What human need does this delight anticipate?
- Does the base task already work reliably?
- Would removing the flourish make the product worse or merely quieter?
- Does motion clarify state, hierarchy, or feedback?
- Is there a reduced-motion equivalent that keeps the meaning?
- Would this still feel considerate on a second and tenth use?
Source essays
- Ten principles for product delight
- On overdoing delight
- On adding homepage delight