motion-design

To make UI animations accessible, you must enforce `prefers-reduced-motion` handling and apply timing constraints to avoid seizure-inducing patterns. This ensures micro-interactions respect user accessibility settings while maintaining safe visual feedback.

For GPU-friendly scroll-linked animations, use IntersectionObserver or ScrollTrigger instead of scroll listeners, and animate transform/opacity properties. This approach prevents DOM manipulation risks and performance regressions during scroll choreography.

Choosing the right easing curves involves applying context-appropriate easing tokens and duration tokens to align UI motion with your design system. This consistency ensures transitions feel unified across all micro-interactions and animation scenarios.

It provides correct usage patterns for GSAP implementation, but explicitly steers away from GSAP-specific code when the intent is framework-agnostic motion principles. You get safe library usage guidance without being locked into a single framework.

UI animations cause performance regressions when using unsafe DOM manipulation or unbounded animation creation. Guard against these issues by constraining animation counts, using timeline composition, and ensuring safe DOM updates to prevent XSS risks.

Yes, you can use framer-motion for UI micro-interactions if you adhere to reduced-motion accessibility, constrain animation counts, and use GPU-friendly properties. This ensures your transitions remain performant and safe under real-world constraints.