Adobe Firefly Video 2.0 — Generative Extend & Object Removal vs Figma AI Make Prototype

“Generative Extend actually solves a real editing problem — you're on the timeline, the clip ends a half-second too soon, and you don't want to reshoot or hold on a freeze frame. The output I've seen from early demos shows convincing motion continuation for static or slow-moving shots; fast action is where the seams show. Object Removal across moving footage is the craftier feature: the tool has to invent believable background through time, not just space, and Adobe's results on mid-complexity backgrounds are genuinely impressive. The taste layer is thin — there aren't many controls beyond 'do the thing' — but for these two very specific jobs, the output quality earns the ship.”

“The output is not cinematic — you're getting sensible default easing curves and standard dissolve transitions, not bespoke motion direction. But that's actually the right call: the taste layer here is deliberately minimal, leaving the designer in control of anything that matters for brand expressiveness while automating the grunt work of wiring 40 frames together. The editing surface is the full Figma prototype panel, which means refinement is identical to hand-wiring, so there's no skill cliff when you need to fix something. The fingerprint is low: generated prototypes are indistinguishable from hand-built ones, which is the correct outcome for a tool like this — you want your design to be the thing with a signature, not the prototype scaffolding.”

“The category here is AI-assisted post-production, and the direct competitors are Runway's video inpainting, Topaz's temporal tools, and whatever OpenAI's video pipeline quietly ships next quarter. What Adobe has that none of those have is the fact that it lives inside Premiere Pro — no round-trip export, no context switching, no 'import your media again.' That integration is the actual product, and it's the reason this ships despite the fact that Generative Extend caps at 50% and falls apart on fast motion. The 12-month kill scenario: Adobe's own model quality lags Runway Gen-4 or Sora-class tools badly enough that pros start tolerating the round-trip anyway. That's the real risk, not a startup competitor.”

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

“The job-to-be-done for both features is sharp and singular: Generative Extend is hired to fix short clips without reshooting; Object Removal is hired to clean up shots in post without a VFX compositing pipeline. Neither requires a new mental model — both surface as tools inside the existing Premiere Pro workflow, which means onboarding is essentially zero for the 10 million editors already in the ecosystem. The completeness question is the right one to ask here: you still can't do heavy-motion object removal without manual cleanup, so this doesn't fully replace a compositor. But for 80% of the editorial object removal cases — mic stands, cables, a stray crew member — this is now the complete solution. That's enough.”

“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 thesis embedded in Firefly Video 2.0 is specific and falsifiable: by 2027, the majority of professional video post-production will involve generative fill rather than reshoots, and the editor who controls that workflow controls the budget conversation. Adobe is betting that being the NLE where these tools live natively — not the standalone AI app you export to — is the defensible position. The second-order effect here is a compression of post-production timelines that shifts power from VFX houses to individual editors with Creative Cloud subscriptions. The trend this rides is the commoditization of temporal video synthesis, and Adobe is right on time — not early. The risk is that model quality, not platform integration, becomes the only thing buyers care about, at which point Adobe's moat is thinner than it looks.”

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