Figma AI Auto-Prototype vs Runway Act-Two

“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 way — a reference clip of someone walking becomes a fantasy character doing the same walk, with weight and momentum that doesn't feel like a puppet. The taste layer here is baked in: Runway has clearly trained on motion data that preserves physical plausibility, so output doesn't collapse into the liquid-limb horror that plagued earlier video gen tools. The editing surface is thin — you get the generation, not a timeline you can keyframe — but for the use case of 'I need this character to do this thing once,' it's actually good enough to ship.”

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

“The direct competitor is Kling's motion transfer and Adobe's Project Neo pipeline, and Act-Two holds up — the full-body fidelity is meaningfully better than what I've seen from Kling on complex locomotion. The scenario where this breaks is multi-person reference footage, fast cuts, or anything requiring consistent character identity across shots: you'll get a good single clip and a continuity nightmare the moment you need a second one. What kills this in 12 months is Sora or a native Adobe tool shipping motion transfer inside an NLE, at which point Runway's standalone credit-burning model competes on price it can't win — but that hasn't happened yet, so ship.”

“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-Two bets on: within three years, the bottleneck for character-driven content will be performance direction, not production cost — and motion transfer is the primitive that makes amateur direction usable. That's a plausible bet, and Act-Two is early enough on the motion-transfer trend line that it's building the training data and user intuition before the curve steepens. The second-order effect nobody's talking about is that this decouples actor likeness from actor performance at scale — reference footage becomes a commodity input, and the implied rights framework hasn't caught up. The dependency that has to hold: Runway needs to maintain model quality leadership for 18+ more months against well-funded Chinese labs that are closing fast.”

“The buyer here is a mid-tier content creator or small studio, and the budget is 'generative AI tools' — a line item that's already crowded and getting scrutinized. The problem is the pricing architecture: credits burn per generation, which means a creator doing iteration-heavy work hits cost unpredictability fast, and the Unlimited plan at $95/mo is the only escape valve. The moat question is the real issue — Act-Two is a feature inside Gen-3, not a product, and Runway's defensibility depends entirely on model quality staying ahead of Kling, Pika, and whatever Adobe ships inside Premiere. The moment a platform player bundles 80% of this into an existing NLE subscription, Runway's standalone pricing story collapses. Good feature, shaky business.”