Google I/O confirmed for May 19–20 — two-day developer keynotes, demos, and pro sessions

Google I/O is Google’s annual developer conference, but the real point is simpler — this is where Google tells app makers what the next year of Android and AI is going to look like. This year’s event is set for May 19 and 20, with the main Google keynote starting at 10 a.m. PT on May 19 and the developer keynote following at 1:30 p.m. PT. Google has also made clear that this won’t just be a single splashy keynote and done — it’s planning two days of livestreamed sessions, demos, and professional-development talks, plus on-demand codelabs after that. (blog.google) ### So what actually got confirmed? The concrete news is the shape of the event. Google locked in May 19–20 for I/O 2026 at Shoreline Amphitheatre in Mountain View, with online access through the I/O site for everyone else. The company has been saying “save the date” since February, but the fuller schedule now shows the event as a two-day program with a consumer-facing Google keynote, a separate developer keynote, and a broader slate of sessions across AI, Android, Chrome, Cloud, XR, and career-focused tracks. (blog.google) ### Why does the two-day format matter? Because it tells you Google is trying to split the audience on purpose. The morning keynote is where the company usually makes the big product promises — the stuff meant for users, partners, and headlines. The developer keynote and follow-on sessions are where Google gets practical and starts telling builders what APIs, tools, and workflows are changing. That separation matters more now because AI announcements can get very abstract very fast, and developers want to know what they can actually ship. (io.google) ### What is Google signaling about AI? Pretty bluntly — AI is the center of gravity. Google’s own preview language points to “latest AI breakthroughs,” Gemini updates, Google AI sessions, and tools for what it calls the “agentic era” of development. In plain English, Google wants developers using AI not just as a chatbot bolted onto an app, but as part of the workflow for writing software and building products that can take actions on a user’s behalf. That is why the schedule keeps circling back to AI coding workflows, autonomous tools, and Google AI Studio. (blog.google) ### Where does Android fit into that? Android looks like the second pillar. Google has already pushed Android 17 deep into beta — Beta 4 landed on April 16 and Google called it the last scheduled beta, which usually means the platform is close enough for serious compatibility testing. That makes I/O the obvious place to turn Android 17 from a developer preview story into a real product story — what changes matter, what new APIs are ready, and what Google thinks app makers need to fix before release. (android-developers.googleblog.com) ### And what about XR and smart glasses? XR is the wildcard, but it’s not random. Google introduced Android XR as a platform for headsets and glasses, and the I/O schedule already shows XR as a named topic area. That does not guarantee flashy new hardware on May 19, but it does tell you Google wants developers thinking beyond phones. Basically, Android is being framed less as a phone OS and more as software that stretches across phones, foldables, cars, desktops, and wearable displays. (blog.google) ### Why are developers paying attention now instead of waiting? Because Google has started the expectation game early. It announced the dates in February, published the livestream schedule in April, and is even teeing up “The Android Show” for May 12 — a week before I/O. That staging suggests Google wants some Android news out in advance so I/O itself can stay focused on the bigger cross-company AI and platform story. (blog.google) ### What should people realistically expect next week? Expect a lot of Gemini. Expect Android 17 to move from beta jargon to practical guidance. Expect Google to talk about AI agents as both developer tools and product features. And expect XR to show up as a long-game platform bet, even if the hardware story is still early. (developers.googleblog.com) ### Bottom line? Google I/O 2026 looks less like a one-day keynote circus and more like a coordinated rollout for Google’s next platform stack — Gemini at the center, Android as the delivery layer, and XR waiting at the edge. The dates matter, but the bigger signal is the structure: Google is telling developers that AI is no longer a side feature. It’s the organizing idea for everything else. (android-developers.googleblog.com)