A component is an API
Figma’s component properties, launched at Config 2022, let a component expose booleans, text and swappable instances instead of a variant for every combination. That makes a design component look like what it always was: an API.
Figma’s Config ran for 24 hours last week, with 15 launches. Auto layout got absolute positioning and negative spacing. FigJam got widgets for Jira, Asana and GitHub. The launch I keep thinking about is the least visual one: component properties.
A component can now expose a boolean (show this icon or don’t), a text property (this is the label) and an instance swap (put a different icon here). Joey Banks, in his newsletter on the launch, hoped it would reduce the combinatorial variant overhead that design system teams have been fighting. He’s right to hope so.
The variant problem
Until now, the main way to make a flexible component in Figma was variants. A button with three sizes, four styles, an optional icon and a disabled state became dozens of drawn combinations. Each one had to be kept in sync by hand. It’s common to find a library with hundreds of them.
Code never worked that way. A button in code takes a few props, and the combinations are computed, not drawn. Component properties move Figma closer to that model. The component describes what can change, and the instance picks.
Design the props
That shift has a consequence people may miss. A component’s properties are its API, and an API needs as much design attention as the screens built from it.
Which things should be properties at all? What are they called? What’s the default? What combinations should be impossible? Those used to be engineering questions answered after the design was drawn. Now the designer is answering them in the file, and whatever they decide is what every other designer on the team can and can’t do.
One component I designed for a dense tool had one shape and a few states. In Uber Studio, an account card showed a rider or driver, said their state in words and offered one button for the next step. Its value was in what it left out. There was no place on it for a second action.
That’s what I’d want design system teams to take from this launch. The fewer, clearer properties a component has, the more consistent everything built from it will be. Component properties make that constraint something you can design on purpose.