Articles

Figma reworked auto layout so it behaves like CSS Flexbox at handoff, closing the small gaps that used to force developers into workarounds to match the canvas. The border-box model is now the default: inside strokes count toward layout like a CSS border, outside and center strokes are excluded like an outline, padding is never squeezed below its set value, and auto gap collapses instead of going negative like space-between. New frames get it automatically; existing frames stay on the legacy version until you upgrade, with a revert option through January 2027.

Admins can now download a CSV showing credit use in beta AI features, giving a fuller picture of AI spend and something to forecast against. Organization and Enterprise plans only.

Rauno Freiberg, a design engineer widely respected for his UI craft, keeps a running collection of short notes on the small decisions that make interfaces feel right. One entry works through why an animation delay meant to highlight a scrolled-to message backfired and felt more awkward; another walks through the redesign of cards. It’s the kind of thinking-out-loud that can teach more than any tutorial.

Luis Ouriach makes the provocative case that when LLMs make code cheap to write, edit, and migrate, the contribution model and the component-as-source-of-truth lose their reason to exist. His point is that consistency was always carried by tokens, not components, so a well-defined token set could govern ten different LLM-generated inputs at once. He stops short of full obituary, asking whether components live on as the unit of constraint.

Anthony Hobday on why most design career advice comes from people who don’t hire designers and reflects a single lucky path. The practical core: a five-minute curriculum, ways to look impressive without impressive jobs, and the signs an org genuinely values interface design. His argument that one strong credential can cover for a weak portfolio pairs neatly with ​“Components Are Dead” below — both circling what actually holds value as the job changes.

The team behind Bud (formerly Orchids), an AI-powered platform for building web apps and internal tools, is joining Figma. Bud was built around the idea that AI could ​“democratize the ability to build software,” and the acquisition fits neatly into Figma’s push into that same territory with Figma Make. The announcement doesn’t say what the team will work on, but the direction isn’t hard to guess.

A deep dive into the principles that separate intentional motion from decoration: easing and timing, anticipation, overshoot, follow-through, hold, and settle. The piece makes a compelling case for grounding animation in real-world physics and film editing rather than trending motion work, and lands on a point worth keeping: as AI tools make quality motion faster to produce, skill and restraint matter more, not less.

Luis Ouriach lays out a clear mental model for design systems at scale: before adding a component, ask whether you actually need a structural change or just a value override. The piece covers theming hierarchy across modes, Extended Collections, and direct token updates; when platform separation is worth the headcount cost (often it isn’t); and why you shouldn’t restructure your system for AI tooling until AI tooling can handle multi-file setups.

Contra Labs put four frontier AI models through a rigorous landing page benchmark: nine professional designers, 40 live HTML artifacts, 540 pairwise matchups across typography, layout, palette, and grid. Sol (GPT 5.6) dominated loosely-specified briefs with an 81–83% win rate, praised for capturing tone the brief ​“only gestured at.” Fable (Claude 5) flipped the result on structured briefs, jumping from 31% to 72% client-readiness when given detailed specs. The real finding is that these models have different philosophies: Sol fills ambiguity with its own taste, Fable waits for yours.

Figma’s third annual AI survey, covering 8,403 product builders across 10 markets, lands on a deceptively simple conclusion: AI is most valuable when it’s a team sport. Two years ago, 7% said AI meaningfully changed how their teams collaborate – this year, that number is 41%. The most cited reason is the canvas — where teams can actually riff together rather than trading prompts solo. The cross-functional blurring numbers are striking too: designers participating in development jumped from 21% to 41%, developers doing design work from 44% to 60%. The role boundaries are dissolving faster than most teams have figured out what to do about it.

A large survey of tech workers in 2026 finds the industry splitting into two groups: roughly half feel amplified by AI, while 14% feel destabilized and 12% are simply resentful. Designers and researchers are overrepresented in the fragile half. What’s striking is that the fear isn’t ​“AI will take my job” — only 22% name that. The bigger worry is unsustainable pace and doing more work for the same pay. Career optimism is down, burnout is up, and 53% would actively discourage someone from entering their field.

Murphy Trueman on the specific thing Figma did that mattered: making abstract structural decisions visible and traceable, in a way that let her understand design systems by actually touching them. She worries that AI assistance is replacing the effortful parts of design work, and there’s a difference between automating the tedious and automating the problem-solving.

Nikolas Klein, PM on Figma Make, walks through how Code Layers work in practice. The mental model is deliberately familiar: duplicate a code layer to explore alternatives the same way you’d duplicate a frame. What’s new is that those alternatives are working experiences your team can interact with, comment on, and prompt against — all in the same file. The extract-to-design flow is the detail worth pausing on: you can pull any state or screen from the code layer back into editable Figma layers, make visual edits, then push the changes back to the code layer and to your repo. Code Layers are in closed beta with a signup for early access.

“AI tends to pull us in deep before we’ve gone wide, and I think that’s a mistake.” Joey Banks’s recap of Config 2026 is a good summary of the features, but the reason to read it is this thread running underneath: the entire Figma canvas strategy this year is really an argument for staying in the messy middle rather than reaching for the polished AI output too fast.

Dylan Field’s own Config 2026 recap, covering all six announcements at once: Code Layers, Figma Motion, Shader fills and effects, Generative Plugins, Weave Tools, and the Figma Agent. His framing: ​“AI has lowered the floor, but it has not raised the ceiling. Designers, creatives, builders: You will raise the ceiling.” A deliberate pushback against the narrative that AI replaces creative work.

Web publishing in Sites and Make has been an all-or-nothing setting. Now admins can set an org-wide default and carve out exceptions per workspace, so security-sensitive teams stay locked down without blocking everyone else.

Mari Kong rounds up four real workflows Figmates are running with the MCP server now that it spans Slides, FigJam, Make, and the Figma agent. Mallory Dean refreshes her AI product launch deck from Slack and Google Drive with one prompt. Prasant Lokinendi generates FigJam kickoff boards from live Asana, Notion, and Hex data. Iris Lin moves designs bidirectionally between canvas and code, ending in a GitHub PR. Yarden Katz drops a code-only screen into Figma, maps it to real components, fixes it with the Figma agent, then pushes it back. None of these are demo scenarios — they’re the actual recurring work.

Matt, designer at Lovable, writes up how they rebuilt their entire color system on OKLCh, derived from just three inputs: a neutral seed, a contrast value, and an accent. The technical choices are solid throughout — perceptually uniform ramps, WCAG contrast by construction, box-shadow borders that composite without layout shift, the state layer — but the most interesting design decision is the intentional reduction of token surface area specifically to make AI-generated UI more consistent. The fewer valid choices a model has, the less it can quietly go wrong.

Christine Vallaure walks through how A2UI, a Google-initiated open protocol, turns a designer’s component catalog into the sole source of truth for AI-generated interfaces. The AI assembles screens fresh for each user request, but it can only name components that already exist in the catalog — so the quality of every screen traces directly back to design decisions made upstream. The interesting flip: the careful work designers often do invisibly, states, tokens, semantic naming, accessibility, stops being a tax and becomes the engine.

“As code becomes cheaper, an increasingly large portion of it is written for prototyping, not production.” Yitong Zhang argues that prototype coding and production coding are diverging into distinct disciplines with near-opposite requirements: prototyping wants speed, mock data, no types, no tests, and wide-ranging agents; production wants the opposite. Cursor, Stripe, and Notion have already shown this with their internal playground environments — and Figma just needs to follow that path. Parallel design exploration means more inference runs, less complexity per run, and better margins than production – making Figma one of the best-positioned companies outside the labs to run agents at scale.