For my latest AI experiment, I’m using Figma Make to build a web analytics product. Right now, Figma Make doesn’t let users download source code, which effectively locks you into the Figma ecosystem.

Of course, in the age of AI, nothing is truly locked. I found a simple workaround: I can take a screenshot of the generated interfaces and have Cursor rebuild them. In fact, I’ve already done this. The catch, however, is that I’m now using AI twice to build the same thing. Given how energy-intensive AI can be, this feels wasteful.

What makes this even stranger is that both Figma Make and Cursor are powered by Claude. From a business or moat-building standpoint, I understand why I can’t hand my Figma Make project directly to Cursor. As a user, though, I find it frustrating. Just make the code portable.

Generating interfaces in Figma Make is easy; managing them, on the other hand, is the hard part. The big challenge is version control. As of now, the platform has no front-end feature for saving specific versions.

Perhaps Git and Claude Code are quietly managing versions in the background. If so, how do they decide what counts as a “significant” version? Furthermore, how does that critical step in the development lifecycle surface in the front end? And ultimately, who did they design this process for—designers, developers, or a new hybrid role?

I’m curious to see how the prompt-to-code lifecycle evolves.