Back
EssayJun ’232 min read

Variables move the source of truth

Figma launched Dev Mode and variables at Config. Dev Mode prices the handoff. Variables are the bigger change: they put a design system’s tokens, and its modes, inside the design file.

Typeface

At Config last week Figma launched two things for the gap between design and code. Dev Mode gives developers their own view of a file: sections marked ready for development, diffs between versions, plugins for Jira, GitHub and Storybook, and an extension for VS Code. It’s free in beta through the end of the year. From 2024 it costs $25 a seat per month on the Organization plan and $35 on Enterprise.

The second launch got less attention: variables. Color, number, text and boolean values, which can point at each other and switch between modes such as light and dark. Prototypes can now use them in conditions and expressions.

The price of Dev Mode will get most of the attention. I think variables are the bigger change.

A design system has always had two copies of its decisions. The design file had a palette and a spacing scale, and the code had its own tokens, and someone kept them in step by hand. When they drifted, which they always did, the code won, because the code is what shipped.

Variables with modes are design tokens with an interface. Once they’re in the file, the design side has a structured copy of the system, one a plugin or an API can read and sync. That’s real progress. It also means the source of truth can now credibly sit in the design tool.

Once tokens live in the design file, editing a variable is editing the product, and it needs the same care as a code change. Today a designer can rename a color or change a mode’s value with no review, no history anyone reads and no idea which screens depend on it.

I’ve worked both ways. On Uber’s experimentation platform I was the only designer, working directly with the engineers building it, and the handoff was a conversation across a desk. That works for one designer. It doesn’t work for a system dozens of teams depend on.

Before a team moves its tokens into Figma, I’d want three things settled:

  • Who can change a variable, and who reviews the change.
  • How a change shows up for the engineers who consume it, before it reaches them.
  • Which copy wins when the file and the code disagree.

The seat price will be argued about for months. The variables panel is where a design system’s governance will get tested.