What Figma Make Is and Why It Matters
Figma Make is an AI-powered design tool that connects directly to live codebases, letting designers visually edit production interfaces while an automated agent updates the underlying code in sync. By turning shipped product surfaces into editable canvases, the Figma Make design tool aims to remove the traditional divide between mockups and real software. Launched in May 2025 and now expanded with new capabilities, Make runs as a Mac desktop beta that plugs into existing development environments. Designers can select an element in the UI, change properties such as size, color or layout, and rely on the AI system to find and modify the relevant code path. Instead of exporting specs or redlines, teams work against the same source of truth, treating production code as part of the design to code workflow.
Visual Code Editing Comes to Live Products
The latest Figma Make update introduces visual code editing for live products, collapsing the gap between the design canvas and the running application. Within the interface, teams can connect to their company’s codebase, pick on-screen components, and adjust properties such as spacing or typography. An AI agent then locates and updates the corresponding code, so designers change the real product, not a static mockup. Annotation-based prompting extends this visual code editing model: designers can describe interactions or animations directly on the canvas, and Make translates those notes into changes in the codebase. This is not a toy environment. Figma Make supports core engineering workflows such as branching, reverting commits, and creating pull requests, so changes flow through standard review and deployment pipelines instead of bypassing developer oversight.
Redefining Designer–Developer Collaboration
By putting production code inside a design tool, Figma Make reshapes designer developer collaboration. Instead of long handoff documents and ticket queues, designers gain a controlled path to propose and implement front-end changes themselves. The new Git workflow support means they can branch from main, experiment visually, and submit pull requests for engineers to review. This reduces back-and-forth over minor layout or copy tweaks, and lets engineering teams focus on architecture, performance and back-end concerns. According to CMSWire, Figma positions Make for designers who already have codebase access, with plans to simplify setup for less technical users. The canvas-to-code loop also works in reverse: screens can move from Make back into Figma Design, keeping visual artifacts and the live product aligned, which reduces miscommunication during rapid iteration cycles.
Toward Integrated Creative Development Environments
Figma Make’s design to code workflow signals a broader move toward integrated creative development environments, where design tools, CMS capabilities and analytics live in a single ecosystem. Figma has expanded quickly beyond its original design suite: it launched Make in May 2025, integrated Anthropic’s Claude into FigJam, acquired headless CMS Payload, and rebranded the AI-native creative platform Weavy as Figma Weave. Serving 13 million monthly active users, the company is building a unified digital experience platform that connects visual design, content and code. One quotable sign of momentum is that Q4 FY2025 revenue reached USD 303.8 million (approx. RM1,397.5 million), up 40% year over year, with Figma Make weekly active users growing more than 70% quarter over quarter. As Make matures, teams can expect tighter loops between experimentation, measurement and deployment inside a single collaborative stack.
Risks, Limits and What Teams Should Do Next
While Figma Make promises faster iteration, it also introduces new responsibilities. Granting designers access to production codebases requires careful role definitions, permissions and education. Teams will need guardrails: branch protections, mandatory code review, and clear conventions for where Make-driven changes are allowed. The current limited beta focuses on Mac desktop users and assumes some level of technical familiarity, so less technical designers may still rely on developers for setup and guardrails. For organizations considering Make, a practical approach is to pilot it on front-end surfaces that change often—marketing pages, design systems, or small UI experiments—before extending it to core product flows. Used thoughtfully, Figma Make can reduce handoff friction, tighten feedback loops, and align teams around a shared source of truth, turning designer developer collaboration into a continuous, code-connected creative process.
