2026-06-01 · Google

How we used Gemini to build Google I/O 2026

models

read at source ↗ blog.google

How we used Gemini to build Google I/O 2026

Source: Google Date: 2026-06-01 URL: https://blog.google/innovation-and-ai/technology/ai/io-2026-google-ai/

Summary

Google used Gemini models extensively across I/O 2026 production: generating a visual identity by feeding five years of I/O guidelines back into the model, building animated short films by combining puppetry with Gemini Omni for cinematic finishing, and powering interactive installations (jellyfish-to-music via Lyria 3 Pro, a generative game using sprite sheets from Imagen). Custom tooling built in Google AI Studio was the consistent integration layer — not off-the-shelf prompting but purpose-built pipelines.

Implications

  • Coding agents / internal tooling. The post is a case study in production AI integration: bespoke tools wrapping foundation models rather than using them directly. That pattern — custom AI Studio pipelines per use case — is where serious internal deployment is heading.
  • Multimodal maturity. Veo (video), Lyria 3 Pro (music), Imagen/Nano Banana (image), and Gemini Omni (general) were composed together for a single event. Orchestrating across modalities in one production is a capability milestone worth tracking.
  • Google-as-its-own-customer. Using I/O itself as the demo is both a marketing move and a forcing function — it signals internal teams are mandated to eat the dogfood, which accelerates integration tooling quality faster than external pilots would.

← all signals