Okay friends, let's say you're building a list component ❖ Which method do you use? A – Using a variant set with options for each amount B – Use booleans to toggle visibility of a single list component

C: @figma creates an iterator slot, where we can choose the number of clones of a component

@figma No one wants slots stop creating drama

A is bad because it’s a mess to scale. Try B+ For a simple list, we create a component with visibility booleans for the default number of items, usually 3, plus one more marked as “4+”. When 4+ is selected, it reveals visibility booleans for the remaining items (5–6 or 5–10).

Yeah that's nice! A+ for your B+

C: create both a list item component (that people can compose themselves) and a generic list component made of 3-6 list items that people can detach and use faster

B but not with boolean properties. Just let the user to hide extra options in the layer tree.

I ended up by creating just a "list item container component" with a "list item component" inside. So you can detach the container and duplicate the list item component as many times as you need and edit them individually in the sidebar. It's not a problem to detach a container.

should add a repeatable property. Like you add variant, instance swap, boolean,.. you should be able to add a “repeatable” property. This way you only have to design a single component variant, and then in the instance property panel you would enter the # of times you wanted repeated. This would be super helpful for listings.

As a designer, B because it’s cleaner. But showing all states to a dev is problematic so sometimes A is needed for visibility.

+1 to everyone saying "wrap the list item in a detachable container"