Fundamentally, it works with every API you can stuff a number into. &quot;Number&quot; includes stuff like hex&#x2F;rgb values and complex strings, too.<p>So yeah, it does work with React, <i>however</i>:<p>1) It will only do CSS value detection (stuff like prefixed values and transform value mapping) if you either give Popmotion a direct reference to the underlying DOM element as if you were using it normally, or manually set a CSS role on Actor init. This only becomes a problem when you&#x27;re working with completely stateless components, but then it could be argued that stateless components shouldn&#x27;t be responsible for their own transitions. This is because:<p>2) No JSX support. I&#x27;ve seen the Velocity React implementation and I&#x27;m not convinced this is the best API (if you haven&#x27;t seen it, check it out: <a href="https:&#x2F;&#x2F;github.com&#x2F;twitter-fabric&#x2F;velocity-react" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;twitter-fabric&#x2F;velocity-react</a>) I wonder if the drive towards JSX-everything isn&#x27;t a misstep and that in some situations things that should be `params` are being made into JSX tags.<p>I don&#x27;t have a wild amount of experience with React so I&#x27;d be interested in hearing your thoughts.<p>And thanks for your opinion on the pay structure, I think we&#x27;re largely in agreement there. Good food for thought.