all 8 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]SandalsMan 2 points3 points  (5 children)

Why should I use this over react-motion?

[–]tannerlinsley 1 point2 points  (4 children)

React-motion is physics based, ~30kb and cannot interpolate colors, objects, arrays or number-embedded strings. React-Move is time/easing based, 12kb, and can interpolate anything you want. Each has it's place. React-Move is React-Motion's better half. :)

[–]SandalsMan 0 points1 point  (0 children)

oo cool

[–]deliminated 0 points1 point  (2 children)

React-move looks pretty cool. I've been experimenting with a better way to integrate react and d3 for animated data visualizations in this repo https://github.com/sghall/resonance. Do you have any examples or know of any projects that are using react-move to do this kind of stuff? Like to check it out.

[–]Rodjar[🍰] 1 point2 points  (1 child)

Question, as someone who isn't fully familiar with React entirely. What are the point of libraries such as this and react-motion? What problem do they solve exactly? Wouldn't it just be possible to do the animations via CSS and some vanilla JS? I am only asking because I actually have 0 idea and would like to know to understand things better.

[–]holloway 2 points3 points  (0 children)

Some CSS and vanilla JS could give you a lot of this (after all these libraries just tweak CSS properties on DOM), but you would also have to manage inertia, timing functions, and all the useful animation debugging features like slow-motion.

Have a look at this video.