Google Stitch Update Targets Figma, but the Claims Are Thin

Google has shipped a major update to Stitch, its free AI design tool, and the framing around it is blunt: can this kill Figma? That question comes from the tool's own coverage, not from Google. It's the kind of claim that deserves stress-testing before anyone reorganizes their design workflow around it.

Stitch generates UI designs from text prompts. The premise is simple. You describe a screen, the model produces a layout, and you iterate. Free access is the headline differentiator — Figma charges per seat, and Stitch undercuts that to zero. But "free" and "good enough for production" are different claims, and conflating them is where most AI tool coverage goes wrong.

What does the update actually change?

Here the record is thin. The source announcing the update leads with the Figma comparison, not with a changelog. No version number appears. No benchmark results appear. No named design system integrations appear. That absence matters. A tool that wants to replace Figma needs to answer for components, constraints, multiplayer editing, developer handoff and version history — the daily mechanics of interface work. None of that is documented in the announcement itself.

What we can say: Google positions Stitch as prompt-driven design generation, free of charge. That's a real workflow change for early-stage exploration, where speed beats fidelity. For production systems work, the evidence isn't in.

Is the Figma comparison fair?

Not yet, on the available evidence. Figma's moat is not the canvas; it's the collaborative layer and the component model that design teams have built on since 2016. A generative tool that outputs screens competes with Figma's first mile, not its last. Killing a platform requires displacing its file format, its plugins and its organizational lock-in. One update doesn't do that. The comparison makes for a good headline — and headlines, I'd note, are exactly what a launch announcement is optimized to produce.

There's also the measurement problem. No user studies, no task-completion data, no error-rate comparisons accompany the update. Without those, "major" is marketing vocabulary, not a finding.

What should design teams watch?

• Whether Stitch exports editable, structured files that survive a real handoff — or just static screens.
• Whether Google publishes usage or retention numbers after the announcement cycle fades.
• Whether the free tier persists, or follows the pattern of AI features that migrate into paid plans once adoption is measured.
• How Figma responds in its own releases, which historically move faster than doom-cycle coverage predicts.

The skeptical read: a free Google tool entering UI generation is genuinely notable, and price pressure on design software benefits buyers. But "kill Figma" is a question the source asks, not a conclusion it supports. When Google ships the changelog, the benchmarks and the export pipeline details, this story earns a second look. Until then, treat the update as a signal of intent — and intent, in this market, is cheap.