Skip to content
Article Figma Oct 2026

Figma: how six teams use code layers for real design work

Code layers, which let designers build code-backed interactive prototypes directly on the Figma canvas, moved into open beta in October 2026. Camille Rose Shortridge at Figma collected accounts from six product and design teams who have been using them in real work. The piece isn’t a feature overview — it’s a set of concrete practice reports from teams with different roles and constraints.

What the case studies cover

Superside’s Leonardo Rica, a motion design lead, built an interactive credit card wallet with scrolling, tapping, and flipping animations. He pushed the prototype through the Figma agent by giving precise values and building the interaction in stages rather than trying to describe the whole thing at once.

Dell’s Miguel Wermuth builds code layers from the same React components developers use, so the prototypes match the shipped product rather than drifting during handoff. He uses the technique to prototype conversational AI experiences and duplicates layers on the canvas to compare alternatives side by side.

Cox Automotive’s Lindsay Brechler, a senior PM, brought a large HTML prototype into code layers to show four pricing tiers for a new CRM feature. She iterated through 19 versions with the agent doing most of the editing, then shared the result as a single HTML file for stakeholder review.

Rocket Money’s Derek Onay rebuilt a design system concept in code using the team’s exact component names, which let the team settle interaction details and check accessibility before the feature reached developers.

Merkle, whose VP of experience design Dave Calleja describes using code layers across the whole process, reports 30% faster iteration and up to 50% less time spent on documentation like interaction specs. That figure is consistent with the broader pattern across the cases: working prototypes communicate interaction details that static frames leave ambiguous.

Checkout.com’s Kris Murphy built a client demo by pulling screenshots of the client’s existing app onto the canvas so the agent could match its style, then sent the result back to the code layer.

Key method

The consistent theme across all six accounts is that static frames force explanation of behavior in annotation and conversation, while code layers make the behavior visible. Teams that iterated heavily — Cox Automotive’s 19 versions, Merkle’s ongoing workflow — found the speed gain significant enough to shift when and how they involve stakeholders.

Who it is useful for

Product designers considering code layers for the first time, design leads evaluating whether to formalize the workflow, and design systems teams looking at how to integrate component names and tokens into agent prompts. The Merkle and Rocket Money accounts in particular are relevant to teams working at scale.