First Look at Figma Make

This was my first time opening Figma Make in its beta period, and I wanted to push it a bit to see what it could actually handle. I started by pasting in a Figma frame of a dashboard design — charts, data tables, the usual — and asked Make to generate an interactive version. It came back with a working prototype that included actual state management, which was more than I expected. The charts responded to interaction, elements had hover states, and the whole thing felt like a real application rather than a clickable mockup.

Pushing it further

Naturally, I had to see where it would break. I asked Make to convert the 2D charts into 3D visualizations using Three.js. This is where the beta label starts to show — it struggled with the Three.js integration, and the results were more “interesting art piece” than “production dashboard.” But honestly, even the imperfect output was useful for understanding what a 3D data visualization could feel like in context. Sometimes a rough version of an ambitious idea teaches you more than a polished version of a safe one.

What makes it useful

The workflow that excites me most is the ability to swap between a live preview and the underlying code, make manual edits to the generated code, and download the whole package. That’s a meaningful bridge between design and development. For testing interactions, validating edge cases, or just getting a feel for how a static design behaves when it’s alive — this fills a real gap. It’s beta, so I’m cutting it plenty of slack, but the foundation is solid. The idea that you can go from a Figma frame to a downloadable interactive prototype without leaving the ecosystem is the kind of workflow improvement that compounds over time.