You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My current problem with the Motion library is that it is almost unusable with coding agents.
I'm using it with Vue and Svelte via the JS version. Agents are usually sure that "Framer Motion" doesn't work with these frameworks, or do some React-only stuff (especially painful with presence and layout animations).
It has no LLM docs, no docs repo, and the site is rendered as an SPA with no content before client-side render, so it is very hard to inform an agent about the current state of the library.
It would be good if basic docs were available in some way or another for programmatic reading.
As I understand, this may be a choice dictated by the business model, which is absolutely
understandable, but IMO this hurts library adoption very much.
I think the additional features, tools, and examples are already good incentives to buy Motion+, but forcing people to buy basic documentation is quite steep, especially when there are alternatives that provide documentation like (who may have thought...) GSAP: https://gsap.com/llms.txt
P.S. But after all, this is just my opinion. You are doing great work and of course may monetize it in any way you want!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
My current problem with the Motion library is that it is almost unusable with coding agents.
I'm using it with Vue and Svelte via the JS version. Agents are usually sure that "Framer Motion" doesn't work with these frameworks, or do some React-only stuff (especially painful with presence and layout animations).
It has no LLM docs, no docs repo, and the site is rendered as an SPA with no content before client-side render, so it is very hard to inform an agent about the current state of the library.
It would be good if basic docs were available in some way or another for programmatic reading.
As I understand, this may be a choice dictated by the business model, which is absolutely
understandable, but IMO this hurts library adoption very much.
I think the additional features, tools, and examples are already good incentives to buy Motion+, but forcing people to buy basic documentation is quite steep, especially when there are alternatives that provide documentation like (who may have thought...) GSAP: https://gsap.com/llms.txt
P.S. But after all, this is just my opinion. You are doing great work and of course may monetize it in any way you want!
Beta Was this translation helpful? Give feedback.
All reactions