One thing I rarely see mentioned in these cases is how vital it is to clarify with the client whether all 550 dropdowns really need to be interactively prototyped. In my experience, clients often just want to see the diversity of values visually, not necessarily interact with them all. Once I switched to using just a few real interactive dropdowns and the rest as static overrides (with clear documentation), I saved hours and still met expectations. Sometimes it’s not a design problem, it’s a scope clarification one.

Client: “I need a form with 1000 inputs, and 550 of them are dropdowns with different values.”

As a designer, you first make one dropdown component with Default, Hover, Active, and Selected states… but then end up creating endless components just to show different values.

Super time-consuming, right?
 

We’ve all been there—Figma community, please tell me I’m not alone! After a day like that, I honestly just unplug and unwind with the mostbet app bangladesh cuz it’s my little escape from dropdown hell.


I’ve already tried using variable properties for different dropdown items.
But here’s the issue: when we copy the dropdown and try to change its values (by opening it in the prototype), it doesn’t work once we close the dropdown again.