Figma’s annual Config conference has always been a window into where the design tool is headed next, but this year’s announcements feel less like incremental feature drops and more like a deliberate attempt to redraw the boundaries of what “design work” even means. The headline additions—AI motion graphics effects and new shader tools—are eye-catching on their own. Yet the bigger story is how Figma is trying to pull more of the creative workflow into a single environment: design, animation, coding-adjacent iteration, and the supporting assets that teams typically bounce between.
At the center of the update is a reimagined canvas optimized for full-stack development. In practical terms, that means Figma is positioning the canvas not just as a place to lay out interfaces or mockups, but as a shared surface where teams can connect design intent to implementation details. Figma describes this as bringing teams, AI agents, tools, and materials “together in one place,” and that phrasing matters. It signals an ambition to reduce the friction that happens when designers, developers, and motion specialists operate in separate tools with separate representations of the same idea.
If you’ve ever watched a project stall because the “final” design is technically final but still not executable—because the code doesn’t match the layout, because the animation behavior isn’t defined, because the visual system needs a shader-like effect that isn’t easily portable—you’ll recognize the problem Figma is aiming at. The company’s approach is to make the canvas more capable of holding the kinds of details that usually live elsewhere.
One of the most consequential additions in that direction is the introduction of coding layers. These are designed to let creators tweak the code of their projects without leaving the Figma Design canvas. That’s a deceptively simple promise. The real value is in the feedback loop: instead of exporting, switching contexts, editing, and re-importing, teams can iterate in a way that keeps the visual and the underlying logic closer together.
Coding layers also change how collaboration can work. Designers often think in terms of components, states, and constraints; developers think in terms of behavior, structure, and performance. When code is embedded as a layer within the design surface, it becomes easier to align those mental models. The design isn’t merely a static artifact waiting for implementation—it becomes a living document where code changes can be reflected visually as part of the same workflow. That can shorten the distance between “this looks right” and “this behaves right.”
Of course, the question is whether this kind of integration actually helps teams or just adds complexity. Figma’s bet appears to be that the canvas can act as a coordination layer. If the coding layer is accessible where the design decisions are made, then the team can treat code as another controllable dimension of the design—not something that arrives late as a separate deliverable. In other words, the canvas becomes a place where intent is expressed in multiple forms at once: visual styling, layout structure, and now code-level adjustments.
That brings us to the other major announcement: AI-generated motion graphics effects. Motion is one of the hardest parts of UI and product design to standardize. Even when teams have strong design systems, animation often becomes a patchwork of bespoke transitions, hand-tuned easing curves, and one-off experiments. It’s not that designers don’t care about motion—it’s that producing consistent, polished animation takes time, and the process is frequently constrained by tooling.
Figma’s new AI motion graphics effects aim to address that by letting creators generate animation and transition options through description. Instead of starting from scratch with keyframes or hunting for the right preset, you can describe what you want and let Figma propose motion outcomes. The immediate benefit is speed: you can explore more variations before committing to a final direction. But there’s a deeper implication too. When motion generation is tied to the design surface, it becomes easier to keep motion aligned with the visuals it’s meant to enhance.
This is where the “push their ideas further” theme becomes more than marketing language. Motion isn’t just decoration; it communicates hierarchy, state changes, and cause-and-effect. If AI can help teams quickly prototype motion behaviors that match the design context, then motion becomes less of a bottleneck and more of an iterative design dimension. Teams can test how a transition feels, how it supports comprehension, and how it reinforces brand personality—without waiting for a specialized motion pass at the end.
There’s also a workflow advantage for teams that include both designers and developers. When motion is generated inside the design tool, it can be easier to translate into implementation. Even if the final animation is built in code, having a motion concept that’s already visually validated reduces ambiguity. Developers aren’t guessing what the designer meant; they’re working from a set of motion behaviors that were created in the same environment as the rest of the design.
The third pillar of the update—new shader tools—points to another kind of creative expansion. Shaders are often associated with advanced graphics pipelines, generative art, and real-time rendering. They’re powerful because they allow effects that go beyond simple gradients and filters: dynamic textures, lighting-like behaviors, distortions, and complex visual transformations. For many product teams, shaders can feel out of reach because they require specialized knowledge and tooling.
By adding shader tools to Figma’s workflow, Figma is effectively lowering the barrier to experimenting with these effects. That doesn’t mean every product design will suddenly become a real-time graphics project. But it does mean designers and creative teams can explore richer visual styles earlier in the process, without needing to jump immediately into a separate graphics environment. Shader experimentation can also support branding and visual identity work—especially for teams building modern interfaces where subtle depth, motion-reactive surfaces, and stylized lighting are increasingly common.
The interesting part is how shaders fit into the broader “single environment” strategy. If Figma is optimizing the canvas for full-stack development and enabling code-level tweaks through coding layers, then shader tools aren’t just a visual novelty. They can become another layer of expressiveness that lives alongside layout and interaction logic. That makes it more plausible for teams to treat advanced visual effects as part of the design system rather than as a last-minute add-on.
And then there’s the AI agent angle, which ties the whole package together. Figma’s announcements repeatedly emphasize “AI agents, tools, and materials” organized together. While the specifics of how each agent behaves can vary depending on the product capabilities and integrations, the underlying idea is consistent: AI shouldn’t be a separate assistant you consult occasionally. It should be integrated into the workflow so that it can help with tasks end to end—automating tedious steps, suggesting options, and reducing manual overhead.
This is where Figma’s approach differs from the simplest “AI feature” pattern. Many tools add a single AI button—generate text, summarize content, create an image. Figma appears to be aiming for something more structural: AI as a participant in the design-to-build pipeline. That includes automation of repetitive tasks, but also orchestration—helping teams move from one stage to the next without losing context.
Consider what that means for real-world teams. In many organizations, the design process involves a chain of handoffs: designers create layouts, developers interpret them, motion specialists refine transitions, and engineers implement interactions. Each handoff introduces risk: misinterpretation, mismatched assumptions, and delays. If Figma can keep more of that chain inside the canvas—especially with coding layers and motion generation—then AI agents can potentially assist at each step while maintaining continuity.
Continuity is the quiet superpower here. When the design surface is the shared reference point, AI suggestions can be grounded in the actual project context rather than generic prompts. A motion effect generated in relation to a specific component state is more likely to be useful than a motion suggestion generated in isolation. Similarly, shader tools applied within the design environment can be tuned to the visual system already in use, rather than requiring a separate translation step.
There’s also a strategic implication for how Figma positions itself against other tools. The design software market has long been split between “design-first” tools and “developer-first” environments. Figma has historically lived firmly in the design-first camp, but it has steadily expanded toward developer workflows. This year’s updates push that trajectory further by making the canvas more capable of representing code-level changes and advanced visual effects.
That matters because the future of product creation is increasingly hybrid. Teams don’t just need static designs; they need interactive prototypes, motion behaviors, and implementation-ready structures. The more Figma can represent those elements directly, the more it can serve as the source of truth. And if AI agents are integrated into that source of truth, then the tool becomes not only a place to design, but a place to accelerate decisions.
Still, it’s worth asking what “optimized for full-stack development” really means in day-to-day usage. Full-stack development is broad: it includes front-end rendering, back-end logic, data flows, and deployment concerns. Figma can’t replace the entire stack. But it can reduce the gap between design artifacts and the front-end layer where many UI behaviors live. Coding layers suggest Figma is focusing on the parts of the stack that are closest to the design surface: component logic, interaction definitions, and code that influences how the UI behaves.
In that sense, Figma’s canvas becomes a bridge. It’s not trying to become a server-side framework. It’s trying to become the place where the UI’s behavior is described in a way that developers can more directly implement. That’s a meaningful shift for teams that currently treat design as a blueprint and implementation as a separate act.
Another unique angle in these announcements is how they reflect changing expectations around creativity. Creators increasingly want to iterate quickly, explore variations, and experiment without committing to a single path too early. AI motion graphics effects support that exploration by generating options from descriptions. Shader tools support it by enabling richer visual experimentation. Coding layers support it by allowing code tweaks without leaving the canvas. Together, they create a