Figma AI Make Prototype vs Runway Act-Three

“The primitive here is code generation from a design IR — Figma's internal node tree is surprisingly information-dense, and using it as the source of truth for code gen is a smarter bet than screenshot-to-code approaches. The DX bet is 'zero config by default, escape hatch for the real engineer' — which is the right call. My concern is the 'real data bindings' claim: if that means hardcoded JSON stubs dressed up as dynamic bindings, the moment a developer inherits this output and tries to wire a real API, the abstraction collapses. The weekend alternative here is v0 or Lovable fed a screenshot — Make Prototype earns its keep only if the generated code doesn't require a full rewrite, and that depends entirely on what the output actually looks like under the hood.”

“This is the first AI feature Figma has shipped that doesn't feel bolted on — it lives at the natural end of the design workflow rather than interrupting it, which suggests the team actually mapped the job before building the feature. The interaction model is sound: designers already think in frames, and treating a frame as a deployable unit respects that mental model instead of asking them to learn a new one. My only structural concern is error states — when the AI misinterprets a component's intent, does the designer get a diff they can understand, or a black-box regeneration? That editing surface will determine whether this is a workflow tool or a demo.”

“The category here is design-to-code, and the direct competitors are Anima, Locofy, and Builder.io — all of which have been promising 'pixel-perfect production code' for three years and consistently delivering 'good enough for a demo.' Figma's distribution advantage is real, but distribution doesn't fix the core problem: design files are rarely production-ready, and the gap between what a designer draws and what an engineer needs to ship is 80% business logic, not layout. This breaks the moment a design has conditional states, authenticated routes, or anything beyond a marketing page. What kills this in 12 months: GitHub Copilot and Cursor already accept screenshots and design tokens; Figma's moat is the file format, not the AI, and that's a thin moat once export formats standardize.”

“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 precise: 'I want stakeholders to experience the design as a working thing, not a click-through prototype' — and Make Prototype nails that job without asking the user to learn a new tool. Onboarding is zero-friction by design since it's a feature inside a product people already have open. The completeness question is where it gets interesting: if this produces a shareable URL with real interactions and data, it replaces InVision, Framer, and ProtoPie for most use cases in one move — but if the output is a Figma mirror that can't be exported or hosted independently, it's a better demo tool, not a workflow replacement. The specific product decision that earns the ship is the same one that made Figma win the first time: making the collaboration artifact and the working artifact the same file.”

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