Figma AI Auto-Layout Suggestions & Content Fill vs Pika 2.2

“Content Fill solves a genuinely tedious design problem — replacing 'Lorem ipsum' and grey boxes with contextually appropriate data so you can actually evaluate a layout instead of imagining it. The auto-layout suggestions are the more interesting feature: they surface the right constraint choices (fixed vs. hug vs. fill) in context, which is where most designers lose time. The specific decision that earns the ship here is that both features operate in-place without breaking the existing frame structure — Figma clearly thought about integration, not replacement.”

“Content Fill produces contextually aware placeholder data — realistic names, plausible product copy, appropriately sized images — which is meaningfully better than the lorem ipsum placeholder era. The taste layer is thin but present: the tool infers from component naming and visual structure what kind of content belongs where, so a card labeled 'user profile' gets a name and avatar, not a product description. The fingerprint problem is real though: all AI-filled content reads like the same anonymous stock internet, so the editing surface still matters, and right now iteration beyond 'regenerate' is limited.”

“The output is the thing here: objects actually stay coherent across frames when you reposition them, which is something Runway and Kling have fumbled repeatedly — you'd move a lamp and watch it shimmer into a different lamp by frame 12. Pika 2.2's scene-consistency hold isn't perfect on fast motion but it's genuinely better. The taste layer is a mixed bag: the restyling presets lean toward the obvious (neon, cinematic, sketch) and there's no granular style input, but the defaults are clean enough that you're not fighting the tool. The editing surface is the real win — being able to iterate on a specific object without regenerating the whole scene is the difference between a demo tool and a production tool.”

“This is the rare case where an AI feature earns its place by being embedded at the exact point of friction — designers have been manually hunting for placeholder content and hand-tuning auto-layout constraints since both features shipped, so the job-to-be-done is real and the integration is correct. The scenario where it breaks is complex design systems with heavily customized component variants, where the AI suggestions either miss the constraint logic entirely or conflict with existing tokens. What kills it in 12 months isn't a competitor — it's Figma itself shipping this deeper into the Dev Mode and variables workflow, making the current GA feel like a stepping stone.”

“The category is AI video editing, and the direct competitors are Runway Gen-3 Alpha and Adobe Firefly Video — both of which have made gestures toward object-level control but haven't shipped it cleanly. Pika 2.2 actually ships it, which earns points. The scenario where this breaks is complex multi-object scenes with overlapping depth: try moving a foreground subject past a background element and the consistency model visibly struggles. What kills this in 12 months: Adobe ships a tighter version of this inside Premiere with native timeline integration and Pika's standalone app value proposition collapses for professional users — the consumer segment stays, the prosumer segment migrates. To stay relevant, Pika needs to nail the API story and get embedded in third-party workflows before that happens.”

“The job-to-be-done is precise: get a design from empty skeleton to reviewable mock without manual data wrangling. Content Fill nails this in under two minutes for standard component structures — you select frames, invoke fill, and the design becomes legible to stakeholders immediately. The product is opinionated in the right direction: it doesn't ask you to configure a content schema, it infers from context. The gap that keeps this from a stronger score is that auto-layout suggestions still require the designer to accept or reject each recommendation individually, which adds friction in bulk-layout scenarios — a 'apply to all similar frames' affordance is conspicuously absent.”

“The job-to-be-done is 'edit a specific element in a video without regenerating the whole thing,' which is genuinely one job and that's good. But the product isn't complete enough to replace the current solution — right now that solution is After Effects plus a motion designer, and Pika 2.2 handles maybe 40% of the cases that workflow covers before you hit a wall. Onboarding gets you to the manipulation interface in under two minutes, which is real, but the tool defers too many decisions to the user: there's no guided flow for 'I want to move this object here' that handles the edge cases automatically, so users who aren't already fluent in video production concepts will generate bad outputs and not know why. Ship this when the tool can handle the full job, not just the easy middle 40%.”

“The thesis here is that AI video stops being a generation tool and becomes an editing medium — meaning the unit of work shifts from 'prompt a clip' to 'compose a scene from manipulable objects.' That's a falsifiable bet: it requires that semantic object understanding in video models continues improving faster than the cost of traditional compositing drops. The second-order effect is significant: if object-level manipulation becomes reliable, the power dynamic between motion designers and clients shifts — clients can now request specific changes without a revision cycle, which either democratizes video production or devalues the motion designer's control over the final frame. Pika is riding the video model capability curve and is roughly on-time — Runway has been here, but Pika's API-first distribution is the differentiator if they execute. The future state where this is infrastructure: every e-commerce product video gets object-swapped for regional markets without a reshoot.”