What Figma Make’s Visual Editing of Live Codebases Really Means
Figma Make visual editing is a workflow where designers edit production code by manipulating on-screen elements in a design tool, while an AI agent updates the underlying codebase in real time. In its latest limited beta for Mac desktop, Figma Make connects directly to a company’s live codebase, letting users select interface elements, tweak properties, and rely on an AI assistant to locate and modify the matching code. The update adds direct visual editing, annotation-based prompting, Git workflow support, and pull request creation without leaving the design canvas. Designers can describe interactions or animations through annotations, then see those instructions translated into code changes. This approach collapses the traditional separation between design artifacts and engineering implementation, positioning visual editing as a legitimate method for production code editing rather than a separate prototyping step.
Collapsing the Designer–Developer Workflow with Production Code Editing
Figma Make is designed to reduce friction in the designer developer workflow by eliminating the constant tool switching that usually happens at handoff. Designers with codebase access can now branch, commit, and open pull requests directly from their design interface, feeding into the same Git pipelines engineers already use. According to CMSWire, the update introduces a canvas-to-code loop, allowing teams to copy screens from Make back to the Figma Design canvas and sync edits into code. That means layout tweaks, state changes, and small interaction updates can move from idea to merged pull request without waiting on a separate implementation pass. Engineering teams keep control through standard review processes, while designers gain a faster path to shipped product, turning visual explorations into production-ready changes with less translation overhead.
Low-Code Design Tools and the Rise of Visual Code Modification
By letting visual edits directly affect production code, Figma Make pushes low-code design tools beyond traditional prototyping into day-to-day development work. Designers can annotate elements to describe behavior, while the AI agent writes or updates code behind the scenes, effectively turning design intent into implementation. This approach aligns with broader low-code trends, where visual editing is no longer a toy environment but a serious path to shipping features. It also reframes code as an accessible medium for non-engineers, providing structured workflows like branching and reverting commits so changes remain safe and reviewable. The beta currently assumes designers already have codebase access, but Figma says it plans to simplify setup for less technical users, hinting at a future where more of the product team can shape production experiences through visual tools.
Figma’s Broader Push into Unified Product and Code Workflows
The expansion of Figma Make sits inside a larger strategy to converge design, content, and development into a unified digital experience platform. The company has evolved from a design collaboration tool into an AI-powered product suite that includes Figma Design, FigJam, Dev Mode, and now Make with live code editing. CMSWire reports that Figma Make weekly active users grew more than 70% quarter over quarter, while Q4 FY2025 revenue reached USD 303.8 million (approx. RM1,394.68 million) and full-year FY2025 revenue crossed USD 1.056 billion (approx. RM4,848.96 million). With Anthropic’s Claude integrated into FigJam and the acquisition of Payload and Weavy, Figma is building a stack where whiteboarding, design, content management, and production code editing all connect. For teams, that means fewer silos between planning, creation, and implementation—and a stronger expectation that design tools participate directly in how code is written and shipped.
Redefining Responsibilities Between Design and Engineering
Giving designers the ability to alter production code from within Figma Make inevitably challenges long-standing role boundaries. Designers can now go beyond specifying intent to changing the actual implementation, which shifts how teams think about ownership, accountability, and review. Engineering still guards quality through Git workflows and pull requests, but designers can influence shipped interfaces in a more direct and continuous way. This can speed iteration on UI details and micro-interactions, while raising new questions about training, code standards, and access control. As more low-code design tools appear, organizations may need new norms around who edits what, and under which safeguards. Figma’s approach suggests a future where design and engineering are less sequential and more concurrent, with visual editing and production code editing treated as two faces of the same workflow rather than separate disciplines.
