Figma AI Site Builder vs Pika 2.5

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

“Scene Ingredients is the feature I've been waiting for since Sora dropped — the ability to say 'put this specific lamp in this specific shot' and have it actually land in a recognizable way is a genuine craft unlock. The Consistent Character Engine doesn't yet hold up over long sequences (faces drift after 4-5 cuts), but for short-form narrative content it's good enough to replace a lot of tedious re-prompting. The output has Pika's house aesthetic — slightly dreamy, a bit soft on motion physics — but that fingerprint is less intrusive than it used to be.”

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

“The Consistent Character Engine is a real differentiator — Runway Gen-3 still fumbles character identity across cuts and Kling's consistency requires tedious reference-image workflows. The scenario where this breaks is exactly what you'd expect: anything beyond 8-10 shots, complex multi-character scenes, or non-human characters with unusual geometry. What kills this in 12 months isn't a competitor — it's OpenAI shipping Sora with native character consistency baked into the API, at which point Pika's moat evaporates unless they've built distribution that sticks. Ship for now, but the clock is running.”

“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 solo creator or small production team on a $24/mo plan — that's a consumer price point competing in a market where Runway, Kling, and soon Google Veo are all fighting for the same wallet. Pika's moat is supposed to be the Consistent Character Engine, but that's a feature, not a defensible position — Runway ships an equivalent in a quarter and the differentiation evaporates. The pricing doesn't survive the inevitable race to the floor: when foundation model video generation becomes a commodity API call, Pika's margin gets squeezed from both ends. I'd need to see either an enterprise sales motion with workflow lock-in or a proprietary dataset play to change this verdict.”

“The thesis baked into Scene Ingredients is falsifiable and important: that AI video generation will shift from prompt-to-clip to asset-assembly, where creators bring their own objects, characters, and props and the model is a compositor, not an author. If that's right — and I think it is — then whoever builds the best object-persistence layer owns the creative production stack. The dependency that has to hold is that foundation model providers don't absorb this at the API layer within 18 months; given the pace of OpenAI and Google's video efforts, that's a real risk. The second-order effect if Pika wins: stock footage libraries become obsolete, replaced by on-demand scene assembly — that's a multi-billion dollar category disruption.”