Figma AI Generative Layouts & Auto-Annotation vs Runway Act-3

“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 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.”

“Act-3's direct competitor is Kling's motion transfer feature and whatever Adobe is quietly shipping into Premiere — and on raw output fidelity for human subject motion, Act-3 is currently ahead on temporal consistency. The specific scenario where this breaks is non-human or highly stylized motion: try transferring a breakdancer's isolations onto an animated character and the model starts hallucinating limbs. What kills this in 12 months isn't a competitor — it's Adobe shipping 80% of this inside a tool 20 million video editors already have open. Runway needs to convert free trials to sticky Pro subscribers before that clock runs out, and 'better motion transfer' is not sufficient lock-in on its own.”

“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.”

“Act-3 produces motion that actually reads as intentional — when you feed it a reference clip of someone walking, the output character doesn't do that AI shuffle where limbs disconnect from gravity. The taste layer here is baked in: Runway has clearly trained on high-quality cinematographic motion, so the defaults lean cinematic rather than uncanny. The editing surface is still limited — you can't keyframe-correct a specific frame that drifts — but the first-pass output quality is high enough that I'm spending time trimming, not re-generating from scratch. That's the craft decision that earns the ship: they optimized for output quality over output volume.”

“The thesis Act-3 is betting on: by 2027, motion capture suits and rotoscoping pipelines get replaced by reference-video-to-scene transfer for 80% of indie and mid-budget production work — and whoever owns the model that does this accurately owns a critical node in the new production stack. That dependency requires two things to hold: reference video quality keeps improving as a training signal, and compute costs drop fast enough that 4K generation becomes a default not a premium. The second-order effect nobody is talking about is that this decouples performance from set — actors can perform in any environment and their motion gets transferred into any generated scene, fundamentally shifting what a 'shoot day' means. Runway is on-time to this trend, not early, which means execution speed matters more than vision right now.”

“The buyer here is a Pro or Unlimited subscriber who is already paying Runway $35-95/mo, so Act-3 is a retention feature, not an acquisition feature — which is fine strategically, but the pricing architecture burns credits per generation at 4K, meaning a working filmmaker doing 50 iterations in a session will hit a wall fast and face a choice between downgrading quality or buying more credits. That's a friction point that sends users to Kling or Pika the moment those tools match quality. The moat Runway is betting on is model quality and brand with professional creators, but there's no proprietary data flywheel here — every generation doesn't make the model smarter for that user specifically. Until they build workflow lock-in beyond 'our generations look better,' this is a features race they will eventually lose on price.”