Code Is Becoming A Design Material
Why this matters to Wen: when code can sit on the canvas beside design, prototypes stop being a fake final draft.
Figma's new code layers let teams import or generate working code directly on the design canvas and move back into editable layers.
The Story
Figma's code-layer announcement cuts at a problem that has quietly wasted enormous creative energy: too many teams still treat the design file as a polished proposal for a product that does not exist yet. By putting working code on the canvas, Figma is trying to turn that proposal into something explorable much earlier.
This changes the kind of judgment a designer can apply. Instead of signing off on a static representation, you can compare working alternatives, extract editable design states back out of code, annotate specifics, and keep the exploration visible to the rest of the team. That is a very different posture from decorating the handoff and hoping the implementation survives it.
Wen should care because Studio Wensday lives in the browser, not in presentation slides about the browser. Any tool that reduces the gap between intended feel and actual behavior gives her more leverage. Taste gets more valuable when it can shape the live version, not only the mock.
Studio Wensday Angle
Take one recurring Studio Wensday component, such as a homepage card or content rail, and rebuild it as a real browser block instead of a static comp. Use that as the unit for future iteration. It is a better way to sharpen both design and editorial judgment.