It's a common sentiment that Figma to code tools don't work well. What exactly is bad about the code that these tools generate? Is it that the code doesn't look consistent with how'd you write it?<p>Plugins either seem to either provide too little detail (Figma Dev mode) or feel too bloated (Anima).<p>Has this been your experience as well? Do you have any alternatives that you've liked?
One problem is that the code tool is usually a one-time code export. After the export, you'll probably want to change the code--add some business logic, event handers, etc. After a while, when the Figma design is changed, there's no way to update the presentational code only without redoing the changes.<p>Plasmic is working on solving this problem! The designs you make in Plasmic are architected for continuous iteration. Disclaimer: I work at Plasmic!
We discussed this ad nauseum at my work a few years back (2019?). We concluded that for the enterprise's designs to truly flow directly from Figma, it would need to be able to export a Material-UI theme (or some similar theme file), so the devs never need to do anything other than just import that theme into their projects.<p>But it couldn't do that. We talked to folks at Figma who were interested in the concept, but we never pursued it beyond early talks. I haven't kept up to see if they have gotten closer to that goal or not in recent years.