![]() ![]() Rumor has it that in TypeScript RTG is required to define styles for each transition which can be annoying. Not very “reacty” – there’s no hook API, only components. A few features make it not suitable for more complex animations – the experience is similar to making animations in CSS. Small bundle size, very easy to use, distinguishes animation events (“entering” | “entered” | “exiting” | “exited” | “unmounted”) that can be styled one by one. We’ve tested many alternatives to Framer Motion but honestly, none of them provide so much flexibility and functionalities – so far it has been irreplaceable. In React’s (and Framer Motion’s) case, we use declarativeness - the way of writing code that represents the effect, thus easy to read and maintain. This imperative approach to animation is hard to maintain due to the descriptive way of writing code. ![]() However, this path is often bumpy when you want to implement anything remotely complex. ![]() When developers think about animations, usually the first method that pops up is pure CSS + conditional playback using JavaScript. Why is it better to use framer-motion than tinker with CSS + JS animations yourself?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |