Figma AI Sites vs Runway Act-Two

“Figma AI Sites solves the single most painful moment in the design-to-web pipeline: the moment a developer opens the Figma file and re-interprets every spacing decision. The output is AI-generated HTML and CSS, which means the tool is only as good as how faithfully it translates auto-layout constraints, component variants, and responsive breakpoints into actual DOM structure — and from what Figma has shown, the fidelity is genuinely high. The specific design decision that earns this ship is that it respects Figma's own component and constraint system as the source of truth rather than screen-shotting the design and guessing. The risk is edge cases: complex interactions, hover states, and scroll behaviors that Figma's prototyping layer doesn't fully express will still fall through the cracks.”

“The primitive here is: static-site generator with Figma as the schema, AI as the compiler. That's actually not a bad idea, but the DX bet is entirely wrong for developers — it routes complexity into the AI black box rather than into a deterministic build step you can debug, version, or extend. The first 10 minutes for a developer means opening the exported HTML and asking whether you can wire up a real CMS, add a custom component, or run it through a build pipeline — and the answer is almost certainly 'not without re-engineering it.' The weekend alternative is real: Webflow, Framer, and even Builder.io solve this problem with more developer surface area and established component ecosystems. The skip is because 'export to custom hosting' without a documented output schema or CLI is just a ZIP file with AI feelings about your design.”

“Category is design-to-code publishing, and the direct competitors are Framer, Webflow, and Builder.io — all of which have been doing this longer, have richer interaction models, and have established CMS pipelines. The specific scenario where Figma AI Sites breaks is the moment a client wants to update a blog post, add a product to an e-commerce section, or change a nav link without asking a designer — the CMS integration claim needs scrutiny because 'CMS integration' on launch usually means 'we support one CMS with five field types.' What kills this in 12 months: Figma's core business is design collaboration, not hosting infrastructure, and the moment this feature requires serious investment in CDN reliability, edge performance, and CMS depth, it either gets spun out or quietly deprioritized. To earn a ship, Figma needs to publish the full capability surface of the CMS layer and show production sites running on it at scale.”

“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 buyer is clear: design-led teams and agencies who already pay for Figma and want to eliminate the handoff cost to a developer or a separate publishing tool like Webflow. The pricing architecture is clever — burying this inside the Professional plan turns it into a retention feature rather than a new SKU, which means Figma doesn't have to win on publishing, they just have to make switching to Webflow slightly less obvious. The moat is the existing Figma file corpus: every team that publishes a site through AI Sites is now locked into Figma as their design AND publishing layer, which is real workflow lock-in. The stress test is whether Webflow or Framer responds by building a Figma import that's good enough — and the answer is they already have import features, so Figma's window to make this sticky is measured in months, not years. The specific business decision that earns the ship is using hosting as an expansion revenue vector inside an existing enterprise contract rather than trying to build a standalone publishing business.”

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

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