Google I/O 2026 Starts Today: Sessions to Watch

Google I/O 2026 opens today with Gemini, Android 17, Googlebook, and Android XR.

Google I/O 2026 begins today, May 19, at the Shoreline Amphitheatre in Mountain View, and the schedule is packed with sessions that matter to anyone building on Google’s stack. The keynote runs 1 hour and 45 minutes, the developer keynote follows for 75 minutes, and the event continues on May 20 with on-demand sessions and codelabs arriving May 21.

What Google wants developers to notice first

The real story this year is not the keynote theater. It is the way Google is trying to make Gemini feel like the system layer across phones, laptops, desktops, cars, and glasses. That shows up in the schedule everywhere, from Android 17 to Googlebook to Android XR.

Google is also making the event easy to follow. The full schedule is live on the official Google I/O 2026 site, and every session streams free on the Google for Developers YouTube channel. No ticket is needed to watch, though signing in at io.google unlocks the full catalog and personal schedule tools.

If you care about what ships next for Google’s platform work, the schedule is already telling you where the company wants attention: AI tooling, Android, web development, and new device categories.

Gemini is the center of gravity

The keynote is expected to open with a major Gemini announcement, though Google has not confirmed the exact version name. The article’s pre-show reporting points to either Gemini 4 or a large Gemini 3.x update, and the practical questions are the ones developers actually care about: context window, latency, pricing, and agent support.

That matters because Google already has scale. Gemini reached 750 million monthly active users by the fourth quarter of 2025, according to developer analysis cited ahead of I/O. Scale helps, but it does not answer whether the model is competitive on benchmarks or cheap enough for real production use.

“The practical questions the keynote must answer are: context window, latency at scale, pricing tiers, and what changes to the agentic framework.”

Google’s own session titles suggest the company wants developers thinking beyond chat. The “agentic era of development” framing points toward autonomous workflows, multi-step actions, and tooling that can move from prototype to production without a pile of glue code.

• Gemini Intelligence is Google’s system-level AI layer for Android.
• Gemma 4 shipped on April 2, 2026 under Apache 2.0.
• Google says Android 17 stable should arrive in June 2026.
• Google Home Speaker is still listed at a $99 price point.

Android 17, Googlebook, and the desktop push

Android 17 is the most important platform session for mobile developers because it appears to be more infrastructure-heavy than visual. Google previewed features such as Pause Point, a 3D emoji refresh, wireless iPhone-to-Android transfer, Gboard’s Rambler mode, and agentic multi-app task completion. The stable developer surface is what matters here, because that is what teams will build against for the next year.

Googlebook is also worth watching closely. It is Google’s new laptop category built on a merged platform that combines Android apps with ChromeOS-style productivity. Five partners are already named: Acer, ASUS, Dell, HP, and Lenovo. Prices and chip details have not been disclosed yet, which makes I/O the first real chance to see whether this is a serious enterprise product or just a brand refresh.

There is a strong business angle here. Google says Chromebooks from 2021 and later will get up to 10 years of automatic security updates, which helps protect current fleets while the company shifts attention toward a new class of devices. For schools and IT admins, that detail matters more than any demo.

• Googlebook is expected to ship in fall 2026.
• Aluminium OS is Google’s Android-based desktop system.
• Android 17 Beta 4 shipped in late April 2026.
• Googlebook has five named hardware partners.

For readers tracking the broader device strategy, OraCore’s earlier coverage of Googlebook and Android XR glasses gives useful background before the keynote starts.

Why the breakout sessions matter more than the keynote

The keynote will get the headlines, but the breakout sessions are where developers will learn whether Google’s story holds up under technical scrutiny. Sessions like “What’s New in Google AI” and “What’s New in Android” are likely to reveal the API changes, tooling updates, and platform limits that actually affect shipping products.

That includes the open-source side too. Day Two includes a session on Gemma, Google’s family of open models, which now matters more because Gemma 4 shipped with Apache 2.0 licensing. That is the first Gemma release with fully commercial-permissive terms, and it changes how teams can think about on-device and self-hosted deployment.

The Android XR track is another signal worth reading carefully. Google has named Samsung, XREAL, Warby Parker, and Gentle Monster as partners, but no consumer Android XR glasses have shipped yet. If I/O gives timelines, it will tell us whether Google is serious about making glasses a real developer target in 2026 or just a long-term demo category.

For comparison, the hardware and platform bets on display today are very different in maturity:

• Gemma already has a commercial-permissive release.
• Android has a stable beta path and a June target for final release.
• Chromebook remains the safe near-term fleet option.
• Android XR still needs consumer shipping dates.

That spread tells you where Google is confident and where it is still filling in the blanks. Gemini and Android 17 are ready for deep technical discussion. Googlebook and Android XR still need the kind of specifics that let teams plan budgets, support policies, and launch timelines.

What developers should watch before the sessions end

If you build with Google tools, the most useful output from I/O will be concrete, not flashy. Watch for model pricing, context limits, and latency claims for Gemini. Watch for Android 17’s final developer APIs. Watch for whether Googlebook gets hardware specs, not just branding. And watch for Android XR timelines that separate real products from prototypes.

My read is simple: if Google gives real numbers today, developers can start planning product work immediately. If it leans on demos and broad promises, the schedule still tells a story, but it is the story of a company trying to align every platform around Gemini before the market decides whether that bet pays off.

The next 48 hours will show whether Google can turn that strategy into details teams can build on, or whether the most important answers get pushed to another event later this year.