Back
NoteDec ’232 min read

Figma stays independent. Your system should too.

Adobe and Figma called off their merger after fifteen months under regulators’ review. The scare is worth keeping: when one tool holds a team’s whole design system, the team should own a copy it can take elsewhere.

Typeface

Yesterday Adobe and Figma ended their merger agreement, fifteen months after announcing it. They saw no clear path to approval from the European Commission or the UK’s Competition and Markets Authority. Adobe’s CEO, Shantanu Narayen, said both companies “strongly disagree with the recent regulatory findings.” Dylan Field wrote that Figma would “continue on as an independent company.”

For designers this is mostly relief. For fifteen months the worry was what Adobe might do to pricing, to the free tier, to the plugins and to the pace of the product. None of that happened, and now it won’t, at least not this way.

I think the scare is worth remembering after the relief wears off, because it showed how much a design team now keeps in one place.

A Figma file used to hold pictures of a product. This year it started holding the system behind them. Since June, variables carry a team’s colors, spacing and modes. Dev Mode is where engineers read the specs. Component libraries hold years of decisions. When a team worried about Adobe, it was worrying about all of that.

A tool that holds everyone’s daily work is infrastructure. I learned what that means at Uber. Studio became the core of Uber’s developer tools, and once most of engineering tested trips in it, every change we made was a change to everyone’s day. That’s a responsibility for whoever owns the tool, and a dependency for everyone who uses it.

Once a tool holds a team’s whole design system, the team should be able to take that system somewhere else. In practice that means two habits. Keep tokens in a format that lives outside the design tool, and sync them in rather than out. And write down the decisions behind the components somewhere that doesn’t need a seat to read, so the reasoning survives a change of tool even if the files don’t.

I’d give the same advice about any vendor that holds a system, Figma included. Figma being independent is good news. A design team being independent of any one company is better.