Figma AI Generative Layouts & Auto-Annotation vs Midjourney Web Editor Inpainting & Reference Layers

“Generative layouts solve the specific, painful problem of component reflow when content changes length — the kind of thing that breaks a design system at the edges. Auto-annotation is the real win here: it closes the gap between the design surface and the developer's mental model without asking either party to change tools. The concern is consistency — if the annotation layer doesn't respect the existing token vocabulary in the file, it produces noise instead of signal, and early beta reports suggest the token mapping is imprecise on complex components.”

“The inpainting brush tool is actually designed — there's a clear mask preview in a distinct overlay color, an undo stack that doesn't blow away your full session, and the strength slider gives you real feedback as you drag, not just after you regenerate. What's missing is any visual hierarchy between the reference layer panel and the generation controls; they sit at the same visual weight and the eye has nowhere to land when you're deciding what to adjust next. The empty-state handling is also lazy — drop into a blank editor with no image loaded and you get a generic placeholder instead of a guided first action. Strong fundamentals, unfinished information architecture.”

“The primitive here is automated design-spec extraction — Figma parses its own component graph and emits structured handoff annotations without a designer manually labeling anything. The DX bet is that removing the annotation step from the designer's workflow also removes the broken-telephone step from the developer's, which is a real problem worth solving. The moment of truth is whether the generated annotations match the token names your codebase actually uses — if they don't, you've traded manual annotation for manual correction, and that's not a win.”

“The direct competitor to auto-annotation is Figma's own Dev Mode, which already does most of this, plus every design-to-code tool in the ecosystem — Anima, Locofy, Supernova — that has been doing automated annotation longer. Generative layouts break the moment a designer has strong layout opinions that don't match the AI's reflow heuristics, which is most senior designers most of the time. What kills this in 12 months: Figma ships it as a core feature included in all plans, commoditizing the beta and making the differentiation moot — the feature survives but the 'new thing' story dies.”

“This is genuinely Midjourney catching up to Stable Diffusion workflows that have existed in ComfyUI and Automatic1111 for two years — credit where it's due for packaging it without requiring a local GPU and a PhD in node graphs. The specific scenario where this breaks is complex product photography: multi-layer references with fine texture like fabric or intricate logos still drift noticeably after inpaint cycles, which means professional retouching workflows aren't fully replaced yet. What kills this tool in 12 months isn't a competitor — it's Adobe Firefly and the Photoshop generative fill team, who now have a direct target to match feature-for-feature. Midjourney wins if their model quality gap holds; right now it does.”

“The job-to-be-done for auto-annotation is clear and singular: eliminate the handoff tax that exists between every designer and every developer in every organization using Figma today. That's a real job with real pain and Figma is the only entity with the right surface area to do it without a plugin. Generative layouts are a separate job — content-adaptive component reflow — and shipping both under one 'Figma AI' banner dilutes the message; these should be two distinct features with distinct onboarding paths, not one beta blob. The product earns a ship because the annotation job is complete enough to replace the current workflow, but the generative layouts piece needs its own moment-of-value story before it pulls its weight.”

“The inpainting actually produces coherent output — fix a hand, swap a background element, adjust a face without nuking the rest of the composition. That's the hard problem other inpainters fumble. The reference layer system is the real unlock: stack a character ref on top of a style ref and the model holds both with real fidelity, not a mushy average. The editing surface is brush-based with adjustable hardness, which is the right call — it matches how illustrators already think about masking. The one failure is the layer stack has no blend mode controls, so if your references fight each other, you can't arbitrate who wins.”

“The thesis here is that non-destructive, multi-reference generative editing becomes a standard primitive in all creative software — not a specialty feature but a baseline expectation, the way layers were after Photoshop 3.0. Midjourney stacking inpainting and reference layers in the same session is a bet that the editing and generation workflows converge into a single surface, eliminating the round-trip between generator and editor that currently fragments creative pipelines. The second-order effect that matters: if this works at quality, it transfers creative leverage from production designers who own the toolchain to art directors and clients who only own taste — and that's a real power shift in agency workflows. The dependency that has to hold is Midjourney's model quality advantage over commodity diffusion endpoints; the moment that gap closes, the web editor is just a UI wrapper.”