What does Figma do next?
Figma solved the problem of making design multiplayer. It might still be solving that problem when the problem has changed.
Figma has a deep collection of useful features.
It also seems to have a problem: a strategic imagination still bound to the canvas.
I realize that’s a challenging thing to say about perhaps the most important product tool of the past decade. This is not a “Figma is dead” article.
Figma changed how digital product teams work. It made design a genuinely multiplayer activity. It made a design file a shared space. Collaboration, critique, exploration, and handoff in a browser-based canvas everyone could see.
Sketch looked comfortable before Figma came along. Users and workflows and plugins, and enterprise legitimacy. A whole ecosystem. InVision for prototypes, Zeplin to support handoff. Abstract for version control.
Then Figma came in like the Kool-Aid Man and made Sketch look obsolete almost overnight.
It wasn’t anything to do with Sketch’s design features. It could still draw a rectangle!
But Figma changed the whole basis of where the two products were competing. Not the design tool with the best interface, but making design collaborative.
I’ve never seen another product that created as much practitioner pressure for change as the internal demand at IBM to switch from Sketch to Figma. It overcame corporate inertia faster than I’d have imagined.
Figma just had better answers. Staying on Sketch meant being left behind.
Figma solved the coordination problem of its moment. Its risk is in continuing to solve the problem after the problem has changed.
There is a historical parallel. But it’s not as glib as “Figma is the new Sketch”. That’s too neat. Figma is clearly larger, more deeply embedded, and has a degree of strategic awareness.
But incumbents don’t usually look like they’re sleeping. Especially from the inside.
Figma is shipping a lot of stuff. And they’re telling a coherent story about the future that runs through them.
Are they building that future, or just extending the conditions that made them dominant before?
The center of gravity is moving from canvas to code.
That means from abstraction to execution. From static artifacts to live systems. And from design files to context that AI interprets and generates from.
Designers will still need visual tools. And teams will need shared spaces for critique and exploration.
But what does Figma do when the canvas is not the center of gravity?
How Figma won in the first place
Figma’s first great achievement was technical. They made the browser matter far more for design than anyone thought possible. Cross-platform access mattered. Performance mattered. Multiplayer mattered.
The product was excellent, and execution counts.
But the deeper shift was cultural.
Before Figma, collaboration was fragmented. It needed local files, redlines, PDFs, and those meetings where everyone asked “is this the right version?” Figma collapsed all that distance.
Figma wasn’t merely a better canvas. Figma was a better coordination model.
It made work around the design abstraction collaborative. Which was a huge step forward.
But an abstraction is still an abstraction.
The canvas is not the product. It’s a representation. The real product is in code.
The canvas was vital for helping us think before the reality of implementation got too expensive.
But it depends on a world where there’s a big gap between visual intent and working software. That’s where the abstraction lives.
AI is collapsing that distance.
The canvas answers a translation problem
The canvas makes sense.
Designers express intent. Engineers translate the intent into code. Product managers mediate priority and scope.
We use the thing we imagined to help us ship the thing that’s real.
And that model isn’t going to be going away any time soon. Many organizations will likely work this way for years to come, if they can get away with it.
But the direction of travel has changed.
Design-to-code is faster. Which is great. But it’s just collapsing the way we already work. Handoff, but faster. Translation, but faster.
What’s genuinely different is how structured design and product context, component code, and rules can be interpreted directly into coded, working interfaces. A prompt no longer has to start from nothing if it has access to the design system, APIs, patterns and engineering constraints.
And design becomes that context. A context for AI execution systems to use.
Teams are still going to need visual comparison and critique. They’ll need shared spaces to make business calls. The terminal window or an IDE is not a place for a lot of stakeholders to participate.
That doesn’t make the canvas central.
Bring it back to the canvas
When I look at Figma’s recent moves, they make sense. They build on its current strength.
More work should happen in Figma. More artifacts should come from Figma. Workflows should come back into Figma. More of the product development should be in the Figma ecosystem.
Reduced to its simplest form, the strategy seems to be:
Bring everything back to the canvas. Our canvas.
But the next era won’t be organized around that.
It’s why I thought “code-to-canvas” was pretty revealing. Make a real thing, then bring it back into Figma as editable frames.
That might solve a short-term collaboration problem. Directionally, it’s strange. Actually, it’s wrong. Wrong for the future, even if useful for Figma’s current position.
In that example, Figma is more worried about getting you back into their room - where they know how collaboration works. Less worried about whether that’s the right model of collaboration for the future.
The canvas won’t be the source of truth
Of course, Figma might be moving towards a more compelling future. One where Figma is a collaborative interface that reflects reality.
But it would be Figma as a lens.
Figma might be where you inspect your working systems. Compare variants. Annotate things that are real. See the design system drift. To steer and govern.
That might be valuable.
It also means accepting the canvas isn’t the center any more. And if it remains important, it only does so if it can be an interface to the truth.
The code, the runtime, what’s real, and what actually ships.
Figma’s danger seems to be trying to remain central by making everything pass through your old model.
That’s an incumbent trap.
That’s looking at what made you dominant in the first place, and only working to improve that thing. And that will be right...right up to the moment that the basis of competition changes.
Figma won against Sketch because it realized the center of gravity could change.
Now that center of gravity is changing again. And Figma is on the other side of the innovator’s dilemma.
Execution is cheap. Coordination is not.
AI makes execution cheaper.
Not free. But from a practitioner perspective, it can feel that way.
AI scaffolds the screens, uses the components, wires them up, refactors and gives us variants. It can create at a speed that changes all the old bottlenecks.
So the limiting factor is not “can we produce an interface?”. The limiting factor is “can you produce the right interface, with the right standards, for the right users, in a way our organization can trust?”
Coordination with AI assistance is not the same as collaboration in a canvas abstraction. We need structured and ranked context.
Which components are approved? Which patterns are deprecated? Which implementation is authoritative when the docs say one thing, the code says another, and Figma says a third? Which accessibility rules apply? Which regulatory constraints matter? Which engineering standards are non-negotiable?
That isn’t a canvas problem.
It’s an infrastructure problem.
Design systems are even more important in this world. Not as component libraries or asset stores, or even as docs for people to manually consult. They’re executable intelligence that tell AI systems how an organization builds.
The canvas is insufficient. It can arrange. It can invite critique. But unless it’s deeply connected to some control layer of product delivery, it risks becoming a pretty picture while the real thing lives elsewhere.
That’s a strategic problem.
What Figma seems to believe
From the outside, Figma seems to believe it can expand its canvas to contain the next era.
And, look, that may be unfair. It’s an external read of a company’s strategy. Figma is full of smart people, with every incentive to understand the shift. It may even be the smart commercial decision. That doesn’t make it the right product model for the next era of work.
Product strategy reveals posture. And Figma’s posture seems focused on a return to canvas.
Bring your generated work back. Bring your coded artifacts back. Bring your developers into Figma. Bring AI into the canvas.
Put more of your organization into the place Figma owns.
Which isn’t necessarily stupid. Enterprises have historically liked consolidation. People are familiar with Figma. And Figma has a gravitational pull from its market dominance.
Figma can keep adding useful capabilities.
Will those capabilities help Figma adapt to a world where the working artifact, and the organizational context, matter more than the design file?
Figma’s bet is: yes, because all of that will come back into Figma.
It’s a bet that the canvas is the core.
And if we change the spaces where we work?
I don’t think the next dominant product workspace will look like Figma with more AI features.
I don’t think it will look like a traditional design tool at all.
More likely, an IDE with some spatial collaboration. Or a browser-based product environment where live software is directly editable, inspectable, and deployable.
It will need to involve an AI orchestration layer that sits across design systems, repos, documentation, analytics, and product management tools.
Some integration of canvas, code editor, staging environment, governance and rules system.
It’s going to look bad at first.
Early versions of what’s right are going to look worse than mature versions of the past. Awkward, incomplete, and easy to dismiss.
Figma should understand this better than most. It won the last round because the future wasn’t just a better design tool, it was a different environment for the work.
The canvas may well remain essential. The canvas-as-abstraction will not.
The canvas needs to be a place to discuss reality, not flatten it.
That is a hard, interesting problem.
What does Figma do next?
I can think of three paths.
A defensive path is to continue to expand the canvas. Build to make more and more work happen inside Figma. That will definitely produce useful features. And it might produce strong revenue. Figma is dominant, and can become stickier and more embedded.
A second path is transitional. Make the canvas more code-aware, and more interactive. Better generation and better workflows. Better import and export. This seems to be where their current moves are. It’s really useful, but it still organizes around the canvas as the product environment.
Or it might accept that the canvas - and thus Figma - won’t be the center of truth. So they build to become one of the best collaborative interfaces into that truth.
That means treating code, product context, design systems, and live behavior as the actual work. And the canvas is just a view into that. A place where teams can reason in a visual way about a system that’s already alive.
I don’t know if Figma wants to make that pivot.
Strategic change isn’t necessarily about seeing into the future. It’s about having to give up on the assumptions that make the present business work.
Multiplayer design isn’t going to go away. It still matters.
The question is where that will live when we can generate, modify, review, and ship product much closer to code.
Figma understood the last change in the center of gravity. Now that center of gravity is moving again.
I’m curious whether Figma follows it.
I’m not a neutral observer.
I’m VP of Product at Knapsack. We’re building in the place where structured design systems and product context meet AI-driven delivery.
Further reading:
Seiz, G. & Kern, A. From Claude Code to Figma: Turning production code into editable Figma designs. Figma Blog, Feb 2026
Banfield, R. Digital Design Isn’t Dead. It Just Got Way More Interesting. Medium, Apr 2025.
The Innovator’s Dilemma. Wikipedia.
Article photo by Krakograff Textures on Unsplash.