What Figma Launched at Config 2026 — and What It Means for Your Team
From code layers to integrated motion: everything Figma announced this week and why it matters for design and development teams.
Last week was Figma's Config. If you couldn't follow it live, here’s what really matters and the implications for our work teams. The main theme this year is clear: the canvas as the place where everything happens — design, code, movement, and generative flows — without jumping between tools.
Code layers: code as a design material, not as a final destination
Figma has introduced code layers. Basically, you can convert any design layer into a code layer with a click — or with a prompt — and work with it in the same file, alongside your team members.
Why does this matter? Because we've spent years dealing with the friction between design and development: what is designed in Figma and what ends up in production are not always the same. This feature doesn't eliminate that gap overnight, but it does introduce a workflow where designers and developers coexist in the same space, iterating on the same material. That’s the real change.
Availability begins in July. You can sign up for the waitlist at figma.com/config-betas.
Motion, shaders, and Weave: the canvas becomes expressive
Three announcements that go in the same direction: Figma wants everything you need to express an idea to be on the canvas and stay there.
Figma Motion arrives with timeline, keyframes, and presets. What previously required After Effects — or at least leaving Figma — can now be built directly within the file. For product design teams, the most relevant aspect is that animations can be integrated into the design system: animate a component once, and that movement propagates to all files using it. In Dev Mode, the timeline is inspectable and exportable directly as CSS, JSON, or React.
Shader fills and effects allow creating complex visual materials from a prompt or reference image, and the result behaves like any other Figma element — with editable parameters and stackable with other effects. Useful for creative direction where visual expressiveness is part of the brief.
Weave tools that previously existed as an independent generative canvas — are now available within Figma. You can build workflows with AI models, connect outputs, iterate, and reuse them as tools. The idea is not to generate random images: it’s to build a visual process that you can inspect and repeat. The creative direction remains yours.
Our interpretation
What we find sensible about this Config is that Figma is not selling AI as a substitute for judgment: it’s betting on a canvas where generative tools are just another material, not the main focus. That aligns with how we work.
Read more news
More recent articles to keep exploring the blog.
November 3, 2026
Lo que la IA recomienda, vuelve en la caja
November 3, 2026
Un toque de IA para las compras de Navidad
October 30, 2026