Hi Joey, I noticed your first tweet about it and thankful for the deep dive in your reasoning 🙏
You are saying how base components undermine usability, but in my team we have a rule “if you have to go to Layers Panel to adjust the component, you’re doing something wrong”, that’s because the API of the component in Figma (true/false or drop downs in Variants panel) is synced with the API in code. If a designer cannot achieve a desired variant through the provided API (Variants panel), this means that this new variant will require a change in code. This rule of ours also solves the “out-of-sync” problem you mention.
Although I've only tuned in a couple of months ago, I'm really enjoying reading and re-reading these articles! It's awesome value, easily digestible and immediately actionable. Fix part of my reading moment in my morning ritual. Just wanted to share my appreciation: thanks man!
Hi Joey, I noticed your first tweet about it and thankful for the deep dive in your reasoning 🙏
You are saying how base components undermine usability, but in my team we have a rule “if you have to go to Layers Panel to adjust the component, you’re doing something wrong”, that’s because the API of the component in Figma (true/false or drop downs in Variants panel) is synced with the API in code. If a designer cannot achieve a desired variant through the provided API (Variants panel), this means that this new variant will require a change in code. This rule of ours also solves the “out-of-sync” problem you mention.
Although I've only tuned in a couple of months ago, I'm really enjoying reading and re-reading these articles! It's awesome value, easily digestible and immediately actionable. Fix part of my reading moment in my morning ritual. Just wanted to share my appreciation: thanks man!