Skip to main content
Jason_Williams
New Participant
January 27, 2021

LAUNCHED: Variables! (Design Token support in Figma)

  • January 27, 2021
  • 110 replies
  • 31711 views

We have been managing our design system(s) for Desktop, Mobile, and TV applications in Figma for some time now and the experience overall has been great (especially with the updated Auto-Layout model) but one thing that has been extremely difficult to manage are design tokens. When I say manage I actually mean we are not using them because there is no solution to do so between Figma and our actual developer component libraries (Apple TV, iOS, Android Mobile, Android TV, HTML TV, HTML Desktop, etc…). We would love to more widely support themes in our apps and at a minimum use tokens for colors, spacing, font weights, and more. This would not only dramatically help with design speed and consistency but allow developers to more easily translate the components and layouts to real platform components (if you could inspect or export the tokens).

Here are a few key items that are quite difficult without first party support for tokens.

  • Color Themes: Without tokens you have to rely on color styles which have a few issues. One the alpha is part of the style so assigning a color style to an auto-layout background requires you to have a color for every alpha variation you may have (ie: modal overlays). We have written a plugin to replace theme colors with another theme but this is a bit of a hack and again can only replace the entire rgba set instead of just the color without affecting alpha. With design tokens and a few UI tweaks this would all go away.

  • Font Styles: Today, Type styles comprise font, weight, line-spacing, etc… which in general is great but if you want a bold, italic, or weight variation you have to create a style for every variant. This would be much more efficient with with tokens (ie. font-face-body, font-face-heading)

  • Spacing: While auto layout is amazing it would be so much better with paddings and gaps being able to be set via token. Today if you decide you want to change the standard gap between list items or card row items you will find yourself drilling down through a lot of components and manually updating pixel values. How much nicer would it be to change the spacing-s token and see everything update! I know some people use spacers but they just muddy design layers and with create so much complexity when auto-layout already supports individual paddings for T,R,B,L. The other issue here is that while you will have a component library the designs that use that library often use frame specific auto-layouts to compose them into the design. This means there is no downstream update to those designs if I want to change the standard margins on the left and right of our designs. Each and every frame (app view) has to be updated. For us that could be hundreds. If the tokens were part of the shared library (like styles) then designers would just use a spacing tokens downstream when laying out a page. This allows me to update the design system and as designers accept the changes in other files the spacing (margins) in this example would just update.

  • Developer handoff: By not having first party support for design tokens the only thing shown in in the inspect window for developers are styles and pixel values. It would be so nice if designers could export JSON and/or CSS variable code that defines the token model to provide developers (or let the developer download / copy them). Then in the inspect window the developer could see the tokens used for colors, padding, and so on.

I know there are plugins out there that attempt to help with this but they are just to fragile because the plugin system does not support modification of the actual Figma UI (which I think is a good thing). However, considering how important tokens are to modern UI design and component development, I feel like this may be something the Figma team is best suited to address.

Here are some quick and dirty mocks on implementation thoughts, based on the current UI. These are just meant to be thought starters so take it with a grain of salt. But I would love to hear what other think. Do others want this feature as well? Are you REALLY wishing we had design token support? Figma team, is there anything on the roadmap for something like this?

110 replies

Zdenek_Culik
March 3, 2023

+1 This feature will be awesome!
🙋

Yannic
New Participant
March 8, 2023

One day! 🙂

March 15, 2023

I would love to finally see Design Tokens implemented natively in Figma. I recently heard rumors that this should be the case anytime this year, but not sure if that’s true. Figma does not publish any roadmap of planned features, does it?

Jeroen2
Active Member
May 3, 2023

From my understanding, the term “Design Tokens” is undergoing a standardization process at large, with many stakeholders (companies, users, developers, designers) involved. This is important, because it will stimulate interoperability between various companies (say, Figma Design Tokens being usable in Zeplin, Zeroheight, Adobe, heck, maybe even Visual Studio or Jetbrains).

Search for “W3C Design Tokens” on the internet to learn more.

There are a few interesting pieces already to be found (at least concerning the progress towards standardization and implementation). But unlike for example the HTML standard, the Design Tokens standard is currently only an Editors’ Draft. That means standardization is not finished yet.

Regarding the rumors: as far as I can read online in the Design Tokens W3C Community Group discussions, Figma is indeed actively working on implementing Design Tokens. But they do run into blockers, which need to be resolved through collaboration in the Design Tokens community. I guess that’s why it is hard to publish a roadmap. Want to learn more about progress, take a look in the community group and more specifically this discussion below every now and then.

https://github.com/design-tokens/community-group/issues/210

StLa1
June 22, 2023

Well I guess this ticket can be closed now

jackbrind
June 22, 2023

Eagerly waiting for a plugin to import a tokens.json file to Figma variables 👀

Sasch
June 22, 2023

@jackbrind I‘ve already created and submitted a plugin that lets you convert your local styles into variables. Not quiet an import/export thing but it will do the job. The plugin is currently in review and will be named „Lightweight Styles to Variables“.

Designing systems that empower gripping experiences at scale.
Ajay_Pawriya
June 22, 2023

@Sasch please keep us updated as soon as you roll this plugin out…

Jason_Williams
New Participant
June 22, 2023

Yeah, I would say the Figma team delivered what I wanted and more on this one. There are some little nice to haves I hope come down the line but I was pretty over the moon yesterday.

XavierV
Active Member
June 22, 2023

Still lot to do but on the right road.