Figma’s Market Dip Isn’t About Design. It’s About Product.

Figma built one of the most influential products in the history of digital design. It changed how designers collaborate, made design more accessible to distributed teams, and turned the browser into a legitimate design environment. For years, it felt almost untouchable.

But the market is changing.

Figma still has enormous brand recognition, a massive community, and a powerful position in the design ecosystem, yet its momentum no longer feels as inevitable. I believe the shift started with the failed Adobe acquisition. When Adobe announced its intention to acquire Figma, it validated just how strategically important Figma had become. But once the acquisition fell apart, Figma was left in an interesting position.

Rather than using that moment to rethink its role in the broader product development ecosystem, much of its evolution continued to focus on making Figma an increasingly powerful environment for designers. Design systems, prototyping, presentations, FigJam, Slides and AI have all added value, but they don't necessarily solve the biggest problem facing modern product teams: the gap between design and shipping.

The Market Has Moved Beyond Designers

The industry doesn't have a shortage of tools for creating beautiful interfaces. It has a shortage of tools that help teams move from an idea to something shipped with less friction. Designers can create sophisticated prototypes, engineers can build sophisticated products, and product managers can define sophisticated requirements, but the handoff between these disciplines can still feel surprisingly similar to what it did years ago. Figma has been extremely successful at owning the design canvas, but the bigger opportunity is owning what happens after the canvas.

At the same time, companies themselves are changing. Organizations are downsizing, teams are becoming smaller, and roles are increasingly being merged together. A product manager might now be expected to understand UX. A designer might be expected to prototype with code. Engineers are getting involved earlier in discovery, while founders, marketers and other non-designers are increasingly capable of creating interfaces with AI-assisted tools. The traditional definition of a "designer" is becoming less relevant, which means the audience Figma needs to serve is getting much bigger. The tools need to become less expertise-oriented without becoming less powerful.

AI is accelerating this shift. The question is no longer simply, "How can we help designers design faster?" It is becoming, "How can we help product teams turn ideas into shipped products faster?" That's a much larger market.

Figma Still Has a Huge Advantage

Figma shouldn't be underestimated. Its community remains one of its strongest competitive advantages. Designers have spent years creating resources, templates, plugins, systems, tutorials and workflows around the platform. That creates an ecosystem that competitors can't simply replicate with a feature launch. Figma has become more than a product. It has become a habit, and habits are difficult to replace.

But community momentum can only carry a product so far. The next generation of product creation is going to be less about which tool designers prefer and more about which tools allow entire product teams to create and ship faster. Figma needs to make its product more accessible to people who don't consider themselves designers while maintaining the depth that professionals expect. Someone should be able to understand an existing design system, make a reasonable change, prototype an idea and move it toward production without needing years of experience with a traditional design tool.

The Next Battle Is Product Shipping

If Figma wants to remain at the very top of the market, I think its strategy needs to move beyond owning design and focus aggressively on product shipping. Imagine a workflow where a product manager defines a problem, a designer explores the experience, an engineer validates the technical approach, and AI helps turn the approved design into production-ready code. The system understands the design system, components, tokens, interaction patterns and technical constraints. The goal isn't for Figma to replace engineering tools or become an IDE. The goal is to make the distance between design and production dramatically smaller.

Figma already owns a huge portion of the product development journey: idea, exploration, design, prototyping and validation. The next opportunity is the second half: build, ship and learn.

The real threat isn't necessarily another design tool. It may be the growing collection of AI-native tools that don't care about traditional product boundaries. These tools are being built around the idea that one person can increasingly do what previously required an entire team. They don't necessarily care whether the person using them is a designer, developer, product manager or founder. They care about the outcome.

If the market continues moving toward outcome-oriented product creation while Figma remains primarily associated with professional design workflows, it risks becoming incredibly important to designers while becoming less central to the overall product development process.

I don't think Figma needs to reinvent itself. It needs to expand what it considers its product. The design canvas is still incredibly valuable, the community is still powerful and the brand is still strong. But the market has moved. Companies are leaner, roles are converging, AI is changing who can create software, and the distance between an idea and a shipped product is becoming the new battleground.

Figma has already proven that it can redefine how teams design. Now it needs to prove that it can redefine how teams ship. The next generation of product design won't be about who can create the best mockup. It will be about who can turn an idea into a great product faster, with fewer handoffs, fewer specialists and less friction.

Figma has already won the canvas. The next opportunity is the product.