Figma Make Reviews

Summary: Five stars from me. Figma Make feels like a major upgrade for product teams because it makes prototyping faster, more interactive, and much closer to real software.

It is not going to replace strong PM judgment, design craft, or engineering review. But for exploring ideas, aligning stakeholders, validating flows, and getting from concept to clickable product faster, Figma Make looks like one of the most useful AI product tools right now.

Positive: Figma Make feels really useful from a product person’s point of view because it closes the gap between “I have an idea” and “people can actually click through it.” Instead of waiting for a full design sprint or a rough engineering spike, I can describe a flow, generate something interactive, and start reacting to it right away.

I especially like that it can start from either a prompt or an existing Figma design. That makes it practical for real product work because most ideas do not start from a blank page. They start from a screenshot, a half-built flow, a customer request, a design file, or a messy stakeholder conversation.

The biggest win is speed of iteration. For product managers, early-stage work is all about testing direction, getting alignment, and making tradeoffs visible. Figma Make gives teams a faster way to explore MVPs, dashboards, internal tools, onboarding flows, and feature concepts before committing serious design or engineering time.

I also like that it keeps the work inside Figma’s ecosystem. That matters because product, design, and engineering teams already use Figma as a shared source of truth. If AI-generated prototypes can stay connected to design references, component logic, and eventually code workflows, that makes the handoff much less awkward.

Negative: I would not treat Figma Make as a replacement for product strategy, user research, or good design taste. It can generate screens and interactions, but it does not automatically know which customer problem matters most, which flow will convert, or which tradeoff is best for the business.

I would also want to test how well it handles complex product states. Simple prototypes are one thing, but real software needs permissions, empty states, error states, loading states, edge cases, admin views, analytics events, and a lot of unglamorous details.

The seat and credit model is also something teams need to understand before building it into their workflow. Some users can fully publish and use Figma Make, while others may only be able to experiment in drafts depending on their plan and access level.