Wow, instance swapping is about to blow the roof off of what we can do with components π€―
Here's how π #config2022
Here's how π #config2022
Yesterday, many people would have said they prefer to avoid nested components...
Why?
Because it's not always clear what is "swappable".
You can use emojis like in the layer list below, but it'll always be a bit confusing when you can edit a component at many different levels.
Why?
Because it's not always clear what is "swappable".
You can use emojis like in the layer list below, but it'll always be a bit confusing when you can edit a component at many different levels.
As a result, people often prefer to expose EVERY variant option at the parent level.
This is super convenient for the design system consumer because all configurations are available at a glance.
But it leads to these massive variant matrixes which are such a pain to manage...
This is super convenient for the design system consumer because all configurations are available at a glance.
But it leads to these massive variant matrixes which are such a pain to manage...
As of today though, you can make nested components configurable at the highest level of a component.
So I can click on this entire `Banner` and still swap a component at the child level (in this case the icon).
Here's why that's a big deal π
So I can click on this entire `Banner` and still swap a component at the child level (in this case the icon).
Here's why that's a big deal π
We can now freely rely on subcomponents without worrying about creating a subpar experience for the consumer of our components π
Because every swappable subcomponent can be configurable at the parent level π
Because every swappable subcomponent can be configurable at the parent level π
β
Win for designers
People consuming components can now see every way they can configure the component at a glance
β Win for design systems
People creating components can use atomic design to minimize truth sources, build more efficiently, and shrink our end variant matrixes
People consuming components can now see every way they can configure the component at a glance
β Win for design systems
People creating components can use atomic design to minimize truth sources, build more efficiently, and shrink our end variant matrixes
Component nesting used to be scary. Not anymore.
@figma has made the entire experience infinitely more friendly.
Big kudos and a genuine thank you from the community π
@figma has made the entire experience infinitely more friendly.
Big kudos and a genuine thank you from the community π
If you're as excited about component properties as I am...
Click into the first tweet and share with others in the community π
Click into the first tweet and share with others in the community π
https://twitter.com/Ridderingand/status/1524118478738796544
Component properties are about to unlock a whole other layer of strategy to building in Figma.
I'll certainly share what I learn on here so follow @ridderingand for more βοΈ
If you haven't explored the playground yet you should definitely check it out πfigma.com/community/fileβ¦
I'll certainly share what I learn on here so follow @ridderingand for more βοΈ
If you haven't explored the playground yet you should definitely check it out πfigma.com/community/fileβ¦
Excited to share some updates with the @figmaacademy community π€
β’ β’ β’
Missing some Tweet in this thread? You can try to
force a refresh
γ
