Figma Code Layers Drag Product Logic Into the Canvas

On Wednesday, Figma code layers turned the company’s design canvas into something closer to a live product workspace than a place for static UI approval. The timing matters because Figma has spent the past year pulling code and AI closer to design, from Figma Make to integrations with Claude Code and Codex, and this update pushes that strategy into the core canvas itself, according to TechCrunch.

This is not a routine feature bundle. It is Figma trying to make the design file the place where product logic starts, before engineering turns an idea into production software.

Wednesday’s Figma code layers push the design file closer to executable product thinking

The sharpest change is the new code layer, which lets teams clone repositories and extract flows from code into design layers for testing. That means the canvas can now hold more than layout, typography, and comments. It can carry implementation detail and interactive behavior in the same collaborative space where designers, product managers, and engineers already debate product direction.

Figma’s chief product officer, Yuhki Yamashita, framed the feature as an exploration tool rather than a production-code generator.

“We think the multiplayer canvas is really powerful because this is an environment where you don’t really care about the quality of the code. If you’re rapidly exploring or need to kind of explore a bunch of new directions, you can do that in this spatial way. We hope that this feature produces different behavior not just with designers, but also with engineers and PMs,” he said over a call.

XOOMAR analysis: that quote is the key. Figma is not claiming the canvas replaces engineering. It is trying to move the messy, early product argument into a shared environment where code can be used as material, not as a final deliverable. That threatens the old handoff model, where design intent gets translated into specs, tickets, and eventually front-end work.

After Figma Make, code layers and motion support attack the static mockup problem

Figma has been working toward this for a while. Last year, it unveiled Figma Make, an AI prompt-based prototyping tool. Since then, it added integrations with Claude Code and Codex to improve the handoff between coding and design. The new update brings that effort inside the canvas.

The update also adds native support for animations, transitions, and 3D transforms. Previously, designers had to create animations in other software and convert them into code Figma could understand. Now those motion details can be created directly inside Figma.

The gain is straightforward: fewer throwaway mockups and fewer approval moments based on incomplete evidence. A stakeholder can approve a screen that looks right but behaves wrong. Motion, transitions, shaders, and code layers reduce that gap.

The risk is just as real. Richer files can become harder to govern. If every team starts generating code layers, motion rules, shaders, and custom plug-ins without ownership rules, the canvas can turn into a junk drawer. Figma is adding power. Enterprises will need discipline.

Later this year, Weavy workflows bring AI production logic deeper into the canvas

Figma also plans to integrate Weavy more tightly. The company acquired the node-based tool last year. Weavy helped designers run workflows through different models to compare outputs, and an update rolling out later in the year will let users generate Weavy workflows directly within Figma.

That matters because the update is not limited to code layers. Figma is expanding the role of its AI assistant across the collaborative canvas. Users can write prompts to create repeatable AI skills, connect tools such as Notion, Granola, Excel, and GitHub, or attach files to give the AI bot more context.

Figma is also adding prompt-based custom plug-in creation. The examples cited are layout generators and vector path tracers. That lowers the barrier from writing plug-in code to describing a task.

XOOMAR analysis: this will split the plug-in world. Niche tools with deep workflows may benefit if AI makes them easier to create. Simple automation plug-ins face pressure if users can generate a replacement from a prompt.

The available numbers show a platform push, but not update-level adoption yet

The supplied related reporting says Figma’s first-quarter revenue grew 46 percent year over year to $333 million, while its net dollar retention rate reached 139 percent, the highest in more than two years. It also says Figma went public in July 2025 at a $20 billion valuation, and that its stock has since fallen roughly 79 percent, trading around $24.

Those figures put the update in a sharper frame. Figma is still growing, but investors are testing whether design software can keep its position as AI coding tools move toward interface generation.

The supplied material does not disclose update-specific usage, pricing, AI feature limits, or how many teams have tested Figma code layers. It also does not quantify how many hours product teams lose translating mockups into specs and front-end work. So the strongest factual claim is narrower: Figma is attacking a known workflow boundary, but it has not supplied adoption metrics for this new layer.

Related reporting also cites competitive pressure from OpenAI’s Codex, Canva, Adobe Firefly, and Google Pics. Figma’s answer is clear: absorb more code and AI into the multiplayer canvas before outside tools route around design files entirely.

Developers, designers, and CIOs now have different fights over the same canvas

Designers get more control over early interaction ideas. That can reduce dependency on engineering during exploration. It also raises the bar. A designer working with Figma code layers, animations, and AI-generated plug-ins is no longer only presenting visual intent. They are shaping product behavior.

Developers may like the clearer intent. Vague specs waste time. A working flow on the canvas can show timing, state, and interaction rules more precisely than a static frame. But engineers will resist any workflow that creates code they must later clean up without clear ownership.

Enterprise buyers will focus on a different question: permission. If Figma’s AI assistant can connect to Notion, Granola, Excel, GitHub, and attached files, then governance becomes central. Who can connect what? Which AI-created plug-ins are approved? Which generated artifacts can influence production decisions?

That same operational discipline appears across XOOMAR coverage of technical and market risk, from 18 Severe Flaws Push Chrome 149 Update Into a Must-Do to Seven-Day Slide Traps NZD/USD Near 0.5650 Support Zone. Different domains, same lesson: tools create value only when teams control the failure points.

The next decision point is whether teams treat code layers as exploration or source of truth

Figma’s strongest path is not replacing production engineering. It is making early product exploration more faithful to what users will eventually experience. If Figma code layers help teams test flows, motion, and interaction logic before the handoff, the canvas becomes harder to bypass.

The weaker path is sprawl. AI-generated skills, shaders, plug-ins, and code layers can fragment design systems if teams create local solutions that never get reviewed. Regulated or brand-sensitive organizations will need explicit rules: assign ownership for generated code, require review checkpoints, document AI-created plug-ins, and decide which prototypes can influence production.

The evidence to watch is simple. If engineers and PMs begin working inside the Figma canvas because code layers make decisions faster, Figma’s platform argument gets stronger. If teams keep treating the canvas as a design-only space and export the hard work elsewhere, this update becomes a powerful feature set with a narrower strategic impact.

The Bottom Line

• Figma is turning the design file into a more active workspace for early product logic.
• The update could bring designers, engineers, and product managers into closer collaboration before production begins.
• By adding code layers and AI-linked workflows, Figma is pushing deeper into the software development process.