Why Adobe XD Failed: The UX Decision Figma Made That Adobe Couldn't Copy

In September 2022, Adobe announced it would acquire Figma for $20 billion. Figma was ten years old, had never been a public company, and launched its first public product the same year Adobe XD did. Regulators blocked the deal. Adobe paid a $1 billion breakup fee. Adobe XD is now in maintenance mode, kept alive by five full-time employees.

This is not a story about a startup getting lucky. It is a story about one product decision made in 2012 that determined everything that followed.

What Adobe Already Had

In 2016, when Adobe released Adobe XD, it was already one of the most dominant companies in creative software. Photoshop and Illustrator had been industry standards for decades. Creative Cloud had locked designers into a subscription ecosystem. Millions of designers already trusted Adobe with their work.

XD was Adobe's direct answer to the growing demand for a dedicated UI and UX design tool. It was fast, native, and capable. It had prototyping, vector editing, and an export workflow that plugged directly into the rest of the Creative Suite.

On paper, Adobe XD should have won without a fight.

The Bet Dylan Field Made Before Anyone Was Watching

In 2012, Dylan Field received a $100,000 Thiel Fellowship - a grant with one condition: leave university and build something. He left Brown University with his classmate Evan Wallace and moved to San Francisco.

Field's framing of Figma was deceptively simple: what if design tools worked the way Google Docs did? Not as a file you saved and sent, but as a shared space that everyone entered together. Wallace had been experimenting with WebGL - a technology that lets browsers render graphics at a quality that previously required desktop software. Everyone Field pitched the idea to pushed back. Building professional design software in a browser felt absurd. One description that circulated internally: like "building a skyscraper with Roombas."

They spent four years building before a single user saw the product. Figma launched publicly in 2016.

The Decision That Couldn't Be Undone

Here is the specific thing Adobe could not copy.

Figma built real-time collaboration into its architecture from day one. Not as a feature added on top of a file-based system. As the foundation the entire product ran on. Every element in a Figma file lives on a server. Every change syncs instantly to everyone in the same file. The browser is not a delivery mechanism - it is the product.

Adobe XD was a desktop-first application. Files lived on your machine. Collaboration was built on top of that architecture, not underneath it.

This matters more than it sounds. You cannot retrofit real-time collaboration onto a desktop-first application the way you can add a new button or change a colour. The entire way data is stored, synced, and rendered would need to be rebuilt from scratch. Adobe would have had to stop being Adobe XD and start over.

What This Looked Like in Real Product Teams

The difference showed up in day-to-day work in ways that compounded over time.

In a file-based workflow, a designer finishes a screen, exports it, uploads it to Dropbox or Drive, and shares a link. The developer downloads it, checks the specs, messages back with questions. The designer updates the file, re-exports, reshares. Every handoff is a transaction.

In Figma, a developer clicks a link and lands in the same file the designer is working in - live, right now. They inspect any element and see its exact properties without the designer exporting anything. A stakeholder leaves a comment directly on the design. The designer responds without leaving the tool.

Figma also made a decision that most design tool companies would have resisted: they gave developers full view and inspect access for free. Adobe XD required a full product license to access design specs. Figma treated the developer as the second primary user of their product - not a consumer of the designer's output. That decision spread Figma across entire organisations, not just design teams.

How the Numbers Caught Up With Adobe

By the time Adobe announced its $20 billion acquisition bid in September 2022, the gap had already closed. Figma held over 80 percent of the interactive product design market by revenue. Adobe XD had 5 to 10 percent.

The UK's Competition and Markets Authority reviewed the deal and concluded that Figma dominated the market it was being acquired from. The EU agreed. In December 2023, Adobe and Figma abandoned the merger. Adobe paid Figma $1 billion - a breakup fee for a deal that regulators concluded would simply eliminate competition rather than create it.

Adobe's general counsel confirmed the XD team had been largely dismantled. Five full-time employees remained, maintaining the product for existing users under contractual obligation. No new features would be built.

Where Things Stand in 2026

On July 31, 2025, Figma went public on the New York Stock Exchange under the ticker FIG. Shares were priced at $33 - above the top of the expected range. On day one, the stock tripled, closing at $115.50 and valuing Figma at nearly $68 billion.

The company that two Brown University students started with a $100,000 fellowship grant - the one everyone said could not be built in a browser - is now worth more than three times what Adobe offered to pay for it.

Adobe XD released its last meaningful update in July 2025: version 59.0.12, a maintenance patch. It is no longer sold as a standalone product to new customers. No new features are planned.

The story that started with one architectural decision in 2012 has its ending.

What This Means Beyond Design Tools

This is not specifically a story about Figma or design software. It is about the kind of product decisions that look small when they are made and enormous a decade later.

The question Figma asked in 2012 was not "how do we build a better design tool?" It was "how do teams actually work?" Designers do not work alone. They work with developers, product managers, stakeholders, and clients. A product built around individual file ownership was answering the wrong question.

Adobe XD answered "how do we build a professional design tool?" It was a good answer to the wrong question.

The same pattern appears in most major product UX failures: the product is well-built, technically capable, and solves the stated problem. What it misses is the surrounding workflow - how the tool fits into the actual context of the people using it. Most SaaS onboarding flows are designed for the individual user, not for the team they will use the product with - and that single oversight is why activation rates stall.