pick-ui-library

Use CSS transitions for user-triggered state changes and keyframes for infinite loops or one-shot entrances. Choose Motion for React when you need real springs, layout animations, or exit animations, and GSAP for timeline-heavy marketing work that does not need springs.

Use Radix Primitives for dropdown menus, dialogs, tooltips, tabs, and selects. It handles keyboard navigation, focus management, and ARIA attributes. Base UI and React Aria are credible alternatives with a nearly identical component shape.

Motion for React (formerly Framer Motion) offers springs with less code and a React-friendly declarative API. React Spring is smaller and more configurable but has a steeper learning curve and requires more code for the same animation.

Yes, use Motion for React's AnimatePresence component. Once React unmounts an element, CSS has nothing left to animate, so AnimatePresence keeps it in the DOM until the exit animation completes.

Avoid a library for simple hover effects, fades, or scroll-triggered reveals. CSS handles hovers, and the Intersection Observer API detects viewport entry without pulling in a heavy dependency. Check package.json first to avoid duplicate animation libraries.

Yes. Code does not stop working because maintenance slows, and Radix remains the base of Vercel's and Linear's design systems. You can patch or fork it if needed, or adopt Base UI knowingly if you want the newer primitive set.