On Motion Design for the Web
Why every animation should earn its place, and how to make them feel cinematic rather than bouncy.
The problem with web animation
Most web animations feel like demos. A bounce here, a spring there, some parallax that serves no purpose. Motion should communicate — hierarchy, state, entrance — not decorate.
Cinematic vs. bouncy
The difference is in the easing curve. Bouncy animations (spring, elastic) feel playful but trivial. Cinematic animations (power3.inOut, expo.out) feel intentional and weighty.
Use power3.inOut for page transitions. Use expo.out for entrances. Use power2.out for micro-interactions. That’s the whole system.
The complexity ladder
Reach for the lightest tool that does the job:
- CSS transitions — 80% of micro-interactions
- CSS + IntersectionObserver — scroll-triggered reveals
- GSAP core — complex timelines
- GSAP ScrollTrigger — parallax, pinned sections
- GSAP Draggable — drag interactions with momentum
If a CSS transition can do it, don’t load a library for it.
Respecting the user
Always honor prefers-reduced-motion. Not “simplified motion” — zero motion. The content should work without any animation at all. Motion is enhancement, never requirement.