AI-powered
podcast player
Listen to all your favourite podcasts with AI-powered features
How to Strike a Balance Between Configurability and Visual State
One of the things that I have found tricky in the past is trying to figure out the right balance between making these super components and eliminating variance. When you see a fully built variant based component, you're seeing every possible visual state that could exist. You want to think more about how is the designer actually going to be using this component? Are those properties relevant to them? Or could you break the component up into separate pieces for different use cases? And so those are the types of things I'm mostly thinking about when I'm using component properties.