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

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

“The sub-200ms latency claim is the only number that matters here, and if it holds outside a controlled demo environment with a consumer webcam and variable lighting, this is genuinely differentiated — most real-time video generation pipelines are nowhere near interactive. The tool breaks the moment you need consistency across multiple takes: character appearance, lighting, and scene context don't persist the way a traditional animation rig would, so anyone trying to build a multi-shot narrative hits a wall fast. What kills this in 12 months isn't a competitor — it's Runway's own roadmap; once they integrate Act-Two into a proper timeline editor with scene memory, the standalone webcam demo becomes a feature, not a product.”

“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 output is a generated character that actually mirrors your body — not just your face, but posture, gesture, and weight distribution — with a latency low enough that the performance feels live rather than queued. The taste layer here is interesting: Runway has made strong default character aesthetics but the motion transfer is the real craft, and it preserves the idiosyncratic quality of your movement rather than smoothing it into generic animation curves. The editing surface is thin right now — you can't easily go back and refine a take the way you would in a timeline editor — but the fingerprint is unmistakably Runway's filmic palette, which reads as premium rather than uncanny in most use cases.”

“The thesis here is falsifiable: within three years, performance capture will be democratized to the point that a single creator with a laptop can produce character-driven video at a quality level that previously required a motion capture stage and a compositing team. Act-Two is an early, credible bet on that claim, riding the convergence of real-time generative video and consumer depth-sensing hardware — it's on-time to this trend, not early. The second-order effect that matters isn't that solo creators make better content; it's that the performance itself becomes the authorship primitive, which shifts power away from production studios toward individual performers and small teams who can now externalize their physicality directly into generated media. The dependency that has to hold: latency and coherence both need to keep improving faster than the novelty wears off.”

“The buyer here is a Runway subscriber who already pays $15–35/month, which means Act-Two is a retention and upsell feature, not a standalone business — and that's fine if it drives tier upgrades, but the pricing architecture doesn't isolate the value to measure whether it does. The moat question is the real problem: the underlying capability is a combination of pose estimation and video diffusion that every major lab is working on, and Runway's edge is execution speed and product integration, not proprietary data or a model nobody else can build. When OpenAI or Google ships this inside a product creators already use daily, the question isn't whether Runway survives — it's whether the feature alone justifies the subscription against an entrenched platform incumbent with free distribution.”