Figma has 90% of the interface design market and a stock price that's 81% down since IPO. That tension defines where the product is right now.
The core product is genuinely good. Browser-based collaboration that actually works, Auto Layout that handles responsive component behavior without needing to understand CSS, a component and variable system that scales well for teams, and Dev Mode that gives developers a reasonable inspection layer without requiring a separate handoff step. The plugin ecosystem has done the work Figma has not prioritized: animation, accessibility checks, content generation, token management. What the core product does not do, a plugin probably handles.
The past two years have felt less focused. The failed Adobe acquisition left the strategy unclear, and the AI features that shipped in 2024 and 2025 have been uneven. Make Designs generates layouts from prompts; the results are functional but generic, and most designers use it as a starting point rather than an output. The better use of Figma's AI is in the smaller places: renaming layers, generating realistic content for placeholders, describing components for accessibility. The big-swing AI features have not landed the way the company needed them to.
Figma Sites is the more interesting bet. Building publishable websites directly from a Figma file, without a developer or an export step, blurs the line between design tool and deployment tool. That's either the right direction or a distraction depending on who you ask. Early output is clean for simple marketing pages; anything more complex hits limits quickly.
The competitive threat is real but slow-moving. Motiff, Penpot, and a handful of AI-native tools are taking runs at different parts of Figma's position, but none have dislodged it at the team level. Enterprise inertia, shared file libraries, and the cost of migrating a whole design system keep most teams where they are. The Figma Weave acquisition in October 2025 suggests the company sees generative media as part of its roadmap, though how that integrates with the core product is still an open question.
For teams doing interface design at any real scale, Figma is still the default. Not because it's the most innovative product on the market right now, but because everything your team has built (components, tokens, design system, developer handoffs) is already there. The interesting question for 2026 is whether AI-native coding tools change that calculus, as designers start working closer to production code and away from static design files.
Latest Updates
How to move fast toward the right thing
With AI, speed comes easy, but so does tech debt. That’s why the best teams don’t just ship something fast; they consider it carefully, build it efficiently, and make it stand out.
Try these 10 skills—and show off your own
Now you can author skills for our agent, directly in Figma, to put your point of view to work. Here are 10 of our favorites to get you started.
Measuring time savings from Figma Make
The Figma Data Science team assumed that AI saves users time—but quantifying it required a new approach to research design.
Better code, fewer tokens: The benefits of Code Connect in MCP
When going from design to code, agents lack the context of your production components. With Code Connect in Figma’s MCP, they get that context. We measured its impact on token usage, task duration, and code quality.
Code, craft, and the making of nested folders
From treating code as a proposal to turning handoffs into conversations, here's how we shaped a new way of working to ship nested folders.
Figma has 90% of the interface design market and a stock price that's 81% down since IPO. That tension defines where the product is right now.
The core product is genuinely good. Browser-based collaboration that actually works, Auto Layout that handles responsive component behavior without needing to understand CSS, a component and variable system that scales well for teams, and Dev Mode that gives developers a reasonable inspection layer without requiring a separate handoff step. The plugin ecosystem has done the work Figma has not prioritized: animation, accessibility checks, content generation, token management. What the core product does not do, a plugin probably handles.
The past two years have felt less focused. The failed Adobe acquisition left the strategy unclear, and the AI features that shipped in 2024 and 2025 have been uneven. Make Designs generates layouts from prompts; the results are functional but generic, and most designers use it as a starting point rather than an output. The better use of Figma's AI is in the smaller places: renaming layers, generating realistic content for placeholders, describing components for accessibility. The big-swing AI features have not landed the way the company needed them to.
Figma Sites is the more interesting bet. Building publishable websites directly from a Figma file, without a developer or an export step, blurs the line between design tool and deployment tool. That's either the right direction or a distraction depending on who you ask. Early output is clean for simple marketing pages; anything more complex hits limits quickly.
The competitive threat is real but slow-moving. Motiff, Penpot, and a handful of AI-native tools are taking runs at different parts of Figma's position, but none have dislodged it at the team level. Enterprise inertia, shared file libraries, and the cost of migrating a whole design system keep most teams where they are. The Figma Weave acquisition in October 2025 suggests the company sees generative media as part of its roadmap, though how that integrates with the core product is still an open question.
For teams doing interface design at any real scale, Figma is still the default. Not because it's the most innovative product on the market right now, but because everything your team has built (components, tokens, design system, developer handoffs) is already there. The interesting question for 2026 is whether AI-native coding tools change that calculus, as designers start working closer to production code and away from static design files.
Latest Updates
How to move fast toward the right thing
With AI, speed comes easy, but so does tech debt. That’s why the best teams don’t just ship something fast; they consider it carefully, build it efficiently, and make it stand out.
Try these 10 skills—and show off your own
Now you can author skills for our agent, directly in Figma, to put your point of view to work. Here are 10 of our favorites to get you started.
Measuring time savings from Figma Make
The Figma Data Science team assumed that AI saves users time—but quantifying it required a new approach to research design.
Better code, fewer tokens: The benefits of Code Connect in MCP
When going from design to code, agents lack the context of your production components. With Code Connect in Figma’s MCP, they get that context. We measured its impact on token usage, task duration, and code quality.
Code, craft, and the making of nested folders
From treating code as a proposal to turning handoffs into conversations, here's how we shaped a new way of working to ship nested folders.