Member-only story

Optimizing Figma variables and components

Lukas Oppermann
UX Collective
Published in
15 min readJun 27, 2024

Our goal is to build a design library that represents our code components as closely as possible. We also want users to be able to change between themes and viewport sizes without having to manually set the properties on every component.

Approach

Using a Card component, I will demonstrate some ideas, techniques and conventions that help us achieve our goal.

The focus is first on a combination of achieving a close match to code with a great user experience for consumers. The secondary focus is on making it easy to maintain. The best case is to achieve both of course.

We start with a new Figma file and add a basic Card component.

A simple card component with a button

Configuration

Currently the component is static. It does not react to any change in our design system or to a change of mode. If we want to use it in a different context, we have to override all its properties.

This approach is called customization¹ and is enabled for all components in Figma by default. In fact, you can’t even disable it. However, customization is something we hardly ever want…

Create an account to read the full story.

The author made this story available to Medium members only.
If you’re new to Medium, create a new account to read this story on us.

Or, continue in mobile web

Already have an account? Sign in

Written by Lukas Oppermann

Product designer with a love for complex problems & data. I post about Figma, design tokens, design systems & design related topics. https://lukasoppermann.com

Write a response

Thanks.

--

Honestly I think Designers should just transition into digital architecture and take all front end related roles. For this is where we headed.

--