Google opens I/O under pressure

Google opened its I/O developer conference on May 19 with a familiar promise and a newer problem. The promise was more Gemini across Android, cloud tools and devices. The problem was that Google arrived at its flagship event while publishers and marketers were still arguing that the company’s AI search products are keeping users on Google instead of sending them outward. That tension matters because Google is now trying to do two things at once. It wants developers to build more aggressively on Gemini, and it wants website owners to accept that AI search is still part of the same search system they have optimized for years. Google’s own documentation now says exactly that: generative AI optimization, from Google’s perspective, is still SEO. Here’s the thread. ### Why did this I/O open under more pressure than a normal product keynote? Google entered I/O with a broader AI story than it had a year ago. Ahead of the conference, the company confirmed it would preview Android XR glasses and said those efforts involved partners including Samsung, Warby Parker and Gentle Monster, part of a wider push to put Gemini into wearable hardware rather than keep it inside phones and browsers. (developers.google.com) May 19 also mattered because I/O is where Google has to show that its AI products fit together. Search, Android, Vertex AI, Gemini app experiences and XR devices are no longer separate demos. They are being presented as one stack, with Gemini as the shared interface layer, according to pre-event reporting and Google’s own partner signaling around Android XR. (androidauthority.com) ### What was Google actually showing? Google’s hardware-adjacent message centered on Android XR smart glasses. Reporting ahead of I/O said Google had confirmed an I/O preview and named Samsung, XREAL, Warby Parker and Gentle Monster as partners building Android XR-powered eyewear. That makes the glasses effort less a single-device launch than a platform pitch to multiple manufacturers and brands. (androidauthority.com) Gemini was also moving deeper into Android and developer products. Separate pre-I/O signals around the Flash model line suggested Google was preparing another fast-turn update cycle for its cheaper, higher-volume model tier, including migration nudges in Vertex AI and sightings of newer Flash variants in testing. Those signs pointed to faster iteration in the part of Google’s model lineup most relevant to app builders. (androidauthority.com) ### Why did a brief Gemini Flash sighting matter to developers? TestingCatalog reported that developers had seen signs of new Gemini Flash upgrades before I/O, including Vertex AI deprecation notices and fleeting model appearances tied to the Flash family. Google had not publicly confirmed those specific sightings at the time of that report, but the pattern suggested a rollout cadence that is getting quicker around multimodal and cost-efficient models. (testingcatalog.com) That matters because Flash is the practical tier for many production workloads. Google’s public Gemini 3 Flash positioning emphasizes lower cost and speed, while still framing the model as capable enough for coding, analysis and interactive applications. For developers, that combination affects whether Gemini is something they experiment with or something they ship. (testingcatalog.com) ### Why are publishers and marketers upset at the same moment? Google published a new Search Central guide on May 15 telling site owners that generative AI visibility still comes back to core search practices. The document says AI Overviews and AI Mode are rooted in Google’s core ranking and quality systems, and explicitly says optimizing for generative AI search is still SEO. (blog.google) At the same time, publisher and marketing reports have argued that AI Overviews are reducing outbound traffic. One widely cited figure in recent trade coverage says click-through rates can drop by as much as 89%, though that number comes from publisher-facing analysis rather than a Google disclosure. The dispute is not really about whether SEO still matters; it is about whether ranking work now produces fewer visits than it used to. (developers.google.com) ### So what is the real issue behind this year’s event? Google’s immediate challenge is coherence. The company is asking developers, device partners and website owners to accept a model in which Gemini becomes the interface for search, software and hardware at the same time. Its official guidance says the web still matters because Google’s generative answers are grounded in indexed pages and supported by clickable links. (searchenginejournal.com) But the business friction is that website owners are increasingly measuring not visibility, but traffic. If AI features surface answers on Google’s page first, then Google has to persuade the broader web ecosystem that inclusion inside those answers is still valuable enough to sustain participation. That is the backdrop for an I/O centered on Gemini everywhere. (developers.google.com) Google I/O continues through May 20, with Android XR demonstrations and Gemini developer updates likely to remain the clearest tests of whether Google can keep partners building while search publishers keep complaining. (androidauthority.com) (developers.google.com)