Figma AI Sites vs Lyria 3 Pro

“Figma AI Sites solves the single most painful moment in the design-to-web pipeline: the moment a developer opens the Figma file and re-interprets every spacing decision. The output is AI-generated HTML and CSS, which means the tool is only as good as how faithfully it translates auto-layout constraints, component variants, and responsive breakpoints into actual DOM structure — and from what Figma has shown, the fidelity is genuinely high. The specific design decision that earns this ship is that it respects Figma's own component and constraint system as the source of truth rather than screen-shotting the design and guessing. The risk is edge cases: complex interactions, hover states, and scroll behaviors that Figma's prototyping layer doesn't fully express will still fall through the cracks.”

“The primitive here is: static-site generator with Figma as the schema, AI as the compiler. That's actually not a bad idea, but the DX bet is entirely wrong for developers — it routes complexity into the AI black box rather than into a deterministic build step you can debug, version, or extend. The first 10 minutes for a developer means opening the exported HTML and asking whether you can wire up a real CMS, add a custom component, or run it through a build pipeline — and the answer is almost certainly 'not without re-engineering it.' The weekend alternative is real: Webflow, Framer, and even Builder.io solve this problem with more developer surface area and established component ecosystems. The skip is because 'export to custom hosting' without a documented output schema or CLI is just a ZIP file with AI feelings about your design.”

“Same API key as Gemini, three-minute output, JSON prompting for structure — this is finally production-ready for apps that need dynamic background music or scored video. The integration with Google Vids is a smart forcing function.”

“Category is design-to-code publishing, and the direct competitors are Framer, Webflow, and Builder.io — all of which have been doing this longer, have richer interaction models, and have established CMS pipelines. The specific scenario where Figma AI Sites breaks is the moment a client wants to update a blog post, add a product to an e-commerce section, or change a nav link without asking a designer — the CMS integration claim needs scrutiny because 'CMS integration' on launch usually means 'we support one CMS with five field types.' What kills this in 12 months: Figma's core business is design collaboration, not hosting infrastructure, and the moment this feature requires serious investment in CDN reliability, edge performance, and CMS depth, it either gets spun out or quietly deprioritized. To earn a ship, Figma needs to publish the full capability surface of the CMS layer and show production sites running on it at scale.”

“Three minutes is still too short for most real-world music use cases, and 'structured sections' often still sound jarring compared to human-arranged music. Suno and Udio are ahead on pure output quality; Lyria's advantage is ecosystem integration, not sound.”

“The buyer is clear: design-led teams and agencies who already pay for Figma and want to eliminate the handoff cost to a developer or a separate publishing tool like Webflow. The pricing architecture is clever — burying this inside the Professional plan turns it into a retention feature rather than a new SKU, which means Figma doesn't have to win on publishing, they just have to make switching to Webflow slightly less obvious. The moat is the existing Figma file corpus: every team that publishes a site through AI Sites is now locked into Figma as their design AND publishing layer, which is real workflow lock-in. The stress test is whether Webflow or Framer responds by building a Figma import that's good enough — and the answer is they already have import features, so Figma's window to make this sticky is measured in months, not years. The specific business decision that earns the ship is using hosting as an expansion revenue vector inside an existing enterprise contract rather than trying to build a standalone publishing business.”

“The integration path is the story here: music generation directly inside the same developer stack as text and video means personalized, dynamic audio becomes a default feature of AI apps, not a special case. That's a massive shift for UX design.”

“Three minutes of structured music that transitions properly is the minimum bar for real creative use. Lyria 3 Pro finally clears it. I'd use this for short film scoring and social video — it's not replacing a composer, but it's replacing stock music licensing.”