For years, the design industry has talked about "design vs code"
And tools (including Figma!) have forced a choice.
But this is a false debate. Code isn't the opposite of design. Code is a material for design.
So we're bringing code to the Figma canvas with Code Layers.
Slots are so much better for Figma performance
Here's my recommendation for the iOS 26 kit, reducing the Segmented Control down from a 14 component variant set, down to a single component with two sub components!
(Note: this is a breaking change)
Imagine a world where you could copy/paste websites into editable Figma layers (jk you donโt have to imagine you can do this now with our Chrome extension)
Everyone says taste is what separates designers in the age of AI.
I donโt buy it. Taste is just recognizing what already looks good โ it excludes anyone without the โrightโ exposure.
Taste, used that way, is just a bouncer at the door.
Fast โ Good โ https://t.co/7dEJcFskLc
@LC_Finch For me the key idea is: fidelity should match confidence. When everything starts polished, we lose the visible signs that something is still WIP.
Writing helps because it keeps the work in the realm of understanding before we turn it into output. Speed is useful, but only later.
@LC_Finch Strongly agree. I wrote about this recently too โ the danger is that AI makes work look resolved before the thinking has actually happened.
https://t.co/S9tkuHvOjS