✨ jennie § yip ✨

That's an incorrect framing of the problem. With design systems features, we have to plan them years in advance. Things like components, variables, and styles are used on the order of billions - one wrong move will result in breaking files and ruining critical design work. We have to be methodical. With Slots, we knew we needed a more performant engine under the hood. On the web, you're only viewing one page at a time. In Figma, you may be viewing 100 variations of that same web page - Figma inherently has to be more performant with the scale people use it at. We knew there would be files out there were more than half of the content on the page would be in a slot, which is why we worked hard on a full revamp of our layout system. We also knew it would be a component property, so we expanded out the pattern of component properties so the mental model would work for slots. Only once those building blocks were in place could we begin implementing it. With DS features, I'm usually planning them around 3 years in advance. The first year is dreaming them, and what the requirements might be. The second year is implementing the foundations and requirements. The third year is building it out and beta testing. Things you saw that launched today were also part of that second year scope - expansions to the surface of the variables modal and its full screen presence will give us the capability to do so much more there in future years. This is how we keep the product reliable with these deeply complex features.