Figma AI Auto-Prototype vs Runway Act-Three

“Auto-Prototype attacks the most tedious interaction in the entire Figma workflow — the rat-clicking through prototype wires that designers do on autopilot while thinking about something else. The specific win is that it infers transition semantics from frame naming and layer structure, which means teams who already maintain clean file hygiene get a disproportionate reward. The risk is that it trains bad habits: designers who rely on AI-generated connections stop building the mental model of how interactions actually chain, and that shows up in handoff and in edge-case coverage. Still, the editing surface remains fully manual, so the output isn't locked — you can correct it, which is the right design call.”

“The output is contextually inferred interaction logic — hover states connected to the right components, screen transitions mapped to obvious navigation patterns — and for 80% of standard flows it is genuinely correct on the first pass. The taste layer here is delegated, not baked in: the AI picks plausible connections, not opinionated ones, which means a checkout flow looks the same as a settings flow until you intervene. That's fine for prototyping speed but not for craft. The editing surface is strong because it's just normal Figma prototype controls underneath, so refinement is frictionless — you're not fighting a new abstraction to fix a wrong assumption.”

“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 direct competitor here is a designer who spends 20 minutes wiring a prototype — and honestly, for anything beyond a linear happy-path demo, that designer still wins on accuracy. Auto-Prototype breaks specifically on complex conditional logic: multi-step forms, authenticated state variations, scroll-triggered reveals. It produces plausible-looking but semantically wrong connections that take longer to fix than building from scratch. The kill vector in 12 months is that this gets commoditized into every Figma tier and the Organization-plan gate disappears, which means the feature is fine but the pricing argument collapses. To earn a ship, it needs to handle conditional branching with real accuracy, not just linear A-to-B screen flows.”

“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 job-to-be-done is sharply defined: eliminate manual prototype wiring so designers can validate interaction flows faster. That's one job, no 'and.' Onboarding is effectively zero — it surfaces inside the existing Figma prototype panel, which means the user reaches value in the time it takes to select frames and click one button. The product opinion is that naming conventions and layer structure are sufficient signal for intent inference, which is an opinionated bet that rewards organized design systems and penalizes ad-hoc files. The completeness gap is conditional logic on complex flows, but for the dominant use case — stakeholder walkthrough demos and basic usability tests — it's complete enough to replace manual wiring today.”

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

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