What is it?
The build of your component in Figma for Designers and product teams.
Why do we do it?
So that designers can use branded components that align with the Design System to quickly create and ship experiences. These libraries are designed to save time for our product teams, allowing them to focus on creating better experiences for customers.
How do we do it?
Consistency in building components with variants and props is crucial for easier maintenance and understanding by others.
Here is an example setup for your components —
Any different variant you might have based on different use cases.
Platform or screen size
|Desktop / large|
|Tablet / medium|
|Mobile / small|
|or pixel value|
For optional attributes or conditional elements.
|Selected — Yes/No|
|Action button — show/hide|
|Optional Messages — show/hide|
Use for all overridable text in components — allow for dynamic text inputs
You want to ensure there is a fine balance between discoverability and flexibility. While it might feel easy just to create one state and rely on colour variables to do the rest, it doesn’t tell our Product Designers what states are available — it also gives them more work and an even greater margin of error.
Hiding too many options behind switches or configurations can confuse designers. Keep key variants visible.
Your Figma file
Layers and pages
Keep your Figma layers and pages clean. When someone uses your library, all of your work is put on display. If your files are messy, it can hurt your credibility and make it harder for people to find the components they need. Additionally, it can cause headaches for maintaining the system, both for you and anyone else responsible for it.
To display all available variations of your component in Figma, use Propstar, a plugin that organises and visualises different variants and options in your master file.
This will make it easier for Designers to discover different component variations and uses.
- Figma component that is accessible and understandable to Designers.