Adobe has “no plans to further invest” in its XD web-design product, which the company put in “maintenance mode” at the outset of its now-scrapped Figma deal
Context & Ripple Effects
Adobe had portrayed Figma as a route to rethink design tools for the cloud era while XD remained a small business after years in market, with XD generating just $15M in ARR after seven years.
As regulators scrutinized the proposed acquisition, a reported remedy path included divesting XD. The transaction was ultimately terminated after Adobe and Figma saw no clear approval path, leaving Adobe to define its design-tool strategy without the deal.
First-order effects
- XD users can expect maintenance rather than further product investment, reducing the likelihood that Adobe closes feature or workflow gaps in the product.
- Adobe formally narrows its commitment to its direct Figma alternative after the failed acquisition, while Figma remains independent.
Second-order effects
- Teams with XD-based workflows gain a clearer signal to assess migration costs and support horizons, benefiting design-tool vendors competing for those accounts.
- Adobe’s design-product positioning becomes more dependent on its remaining portfolio rather than a renewed standalone XD challenge to Figma.
Third-order effects
- The episode illustrates how blocked consolidation can force incumbents to make explicit portfolio choices instead of using acquisitions to resolve weak product positions.
- If this pattern persists, collaborative design software may remain more competitively fragmented, with product execution and user-workflow lock-in—not acquisition—deciding market share.
The trend: Antitrust resistance to major software acquisitions is pushing incumbents to clarify whether they will rebuild, maintain, or exit overlapping products.