Figma AI Site Builder vs Runway Act-Three

“The component-aware generation is the actual design decision that earns this a ship — it means generated layouts use your real spacing tokens, your actual button variants, your defined type scale, not a hallucinated approximation of them. That's the difference between a tool that creates cleanup work and one that creates a starting point. The caveat: it still leans heavily on auto-layout defaults that produce structurally correct but visually predictable grids, so if your design system is expressive rather than utilitarian, the outputs will flatten it. But compared to every other AI layout tool that ignores your existing system entirely and forces a manual remap, this is a meaningful step toward AI that respects craft.”

“What this actually produces is a responsive grid that slots your real components into sensible hierarchy — hero, nav, content sections — which sounds modest until you remember every other AI design tool hands you a Figma file full of ungrouped rectangles pretending to be a design system. The taste layer here is partially baked-in and partially delegated: Figma's model has learned layout conventions, but the tokens and components you've defined do the aesthetic heavy lifting, which means the output quality ceiling is directly tied to how mature your design system is. The editing surface is native Figma, which is genuinely good news — you're not trapped in a generation-only interface — but the AI doesn't yet understand iterative prompts like 'make this section feel less corporate,' so the refinement loop still drops back to manual.”

“The output is genuinely uncanny in the right direction — mouth shapes follow phonemes rather than averaging them into a blur, and eye movement has micro-saccades that make the face feel inhabited rather than puppeted. The taste layer is baked in: Runway has made strong decisions about what 'natural' looks like and the defaults hold up. The editing surface is shallow though — you get one pass at timing and expression intensity, and if the audio-driven movement doesn't feel right, your recourse is re-prompting rather than keyframing. The fingerprint is there if you know what to look for (a certain smoothness in head movement transitions), but it's subtle enough that most audiences won't clock it. The craft decision that earns the ship: they prioritized believability in the upper face over perfect lip sync, which is the right call — humans read emotion from eyes first.”

“The component-aware angle is the only thing that distinguishes this from the dozen AI layout generators that already exist, and it's a real differentiator — when it works. The scenario where it breaks is the one most teams actually face: design systems that aren't perfectly structured, with inconsistent naming conventions, missing variants, or components that predate auto-layout. Feed it a messy real-world library and the generation quality degrades to the same generic output you'd get from any competitor. What kills this in 12 months isn't a competitor — it's Figma itself shipping a more capable version bundled deeper into the product, making the current feature feel like a preview rather than a destination. Ships because it solves a real problem for teams with mature design systems, but that's a narrower user base than Figma's marketing implies.”

“Direct competitors are HeyGen and D-ID, both of which have been doing audio-driven avatar animation for two years — so the category isn't new. What Act-Three actually does differently is animate non-avatar characters: illustrated figures, stylized portraits, fictional characters from concept art, not just photorealistic headshots. That's the real differentiator and Runway should be saying it louder. The scenario where this breaks is any character with an unusual face structure — highly stylized art with asymmetric features, animals, or side-profile images all produce artifacts that break the illusion immediately. What kills this in 12 months: HeyGen ships stylized character support and undercuts on price, because Runway's model costs scale faster than their subscription tiers suggest. What would have to be true for me to be wrong: Runway has quietly built proprietary training data on non-photorealistic characters that HeyGen can't replicate cheaply.”

“The buyer is already a Figma Professional subscriber, which means this feature has zero new sales motion — it's pure retention and upsell insurance against competitors like Framer AI and the growing list of design-to-code tools threatening Figma's seat count. The moat here isn't the AI generation itself, it's the component graph: Figma already owns the design system artifact for most mid-size product teams, so a generation feature that reads that artifact is structurally harder to replicate than a standalone AI layout tool. The business risk is that this accelerates the timeline to 'one designer instead of three,' which is good for Figma's enterprise retention story but creates real pricing pressure as the per-seat model gets harder to justify. Ships because it strengthens Figma's platform lock-in at exactly the moment competitors were starting to find footholds.”

“The buyer here is a content creator or small studio who pays out of the Runway subscription they already have — Act-Three is a feature, not a product, which means Runway captures the value through subscription retention rather than direct pricing. That's fine for Runway as a company, but it means Act-Three lives or dies by whether it drives Runway plan upgrades, and I'm skeptical it does at the current quality tier for professional buyers. The moat question is brutal: HeyGen has a head start in the enterprise avatar market, Kling and Hailuo are compressing the consumer market from below, and Act-Three is wedged in the middle with no obvious distribution advantage. What would need to change: Act-Three needs to either go upmarket into a dedicated API product with per-second pricing that studios can actually budget for, or become the clear quality leader with a public benchmark. Right now it's neither.”

“The thesis Act-Three bets on: within three years, the cost of character animation drops below the cost of casting voice actors, which collapses the economic barrier for indie game cutscenes, educational simulations, and localized marketing. The dependency that has to hold is that generated motion stays legally distinct from the reference image subject — if a court rules that animating a real person's photo requires their consent for every output frame, this use case evaporates for commercial work. The second-order effect that matters: this doesn't just speed up animation, it shifts creative power to writers and concept artists who've never had access to motion tools. The scenario where this is infrastructure: a game studio uses Act-Three to generate all NPC dialogue animations in 48 hours instead of a 6-week mocap pipeline. Runway is early on the non-photorealistic animation trend line, and early is where the moat gets built.”