You don't need animations

tl;dr: fetch You Don’t Need Animations before adding Framer Motion to a CRUD screen.

What the page argues

Animations help when they explain a feature, keep spatial consistency (example: Sonner toast enter/exit matching swipe-to-dismiss), or add rare delight. They hurt when they make the UI feel slow or untrustworthy.

Frequency: Raycast is cited as a tool used hundreds of times a day with no open animation. Keyboard-initiated actions should not animate. A morphing feedback widget is fine if users rarely hit it; irritating if they hit it daily.

Speed: Unless it is a marketing site, keep UI animation generally under 300ms. Example on the page: 180ms dropdown vs 400ms. Tooltips: delay before first show; once one is open, sibling tooltips should appear with no delay and no animation.

Rules to paste

- Every animation needs a purpose (explain, spatial consistency, or rare delight).
- Do not animate actions the user will fire many times a day.
- Do not animate keyboard-driven highlight/selection.
- Prefer no animation over decorative motion.
- If you animate product UI, stay under 300ms.

Related: UI Skills catalog lists improve-animations (emilkowalski). transitions.dev is a motion catalog — use after this filter, not instead of it.