Google I/O: Sidekick and Gemini discovery move the Android funnel again

Google I/O ran May 19 and 20, and two announcements matter more to UA teams than the keynote's headline demos. The first is Play Games Sidekick, an in-game AI overlay that gives players tips and social features without leaving the app. The second is app and game discovery inside the Gemini app itself, on Android as well as on the web.

Sidekick and the first-session experience

Sidekick is the more immediately interesting one for creative and retention teams, even though it isn't a UA product on paper. An overlay that can explain a mechanic or suggest a next move changes what a first session looks like for a player who might otherwise bounce off a confusing tutorial. If Sidekick reduces early-session confusion at scale, it should show up as a lift in D1 retention for participating titles before it shows up anywhere in acquisition reporting. Teams running hybrid-casual or midcore titles with a steep onboarding curve have a reason to track Sidekick rollout closely; it competes with in-house tutorial design for the same job.

Gemini discovery and the Android funnel

Gemini-based discovery has the more direct line to acquisition. Google has spent the last two years trying to make Play Store search and recommendations smarter without changing where users go to find apps. Putting discovery inside Gemini instead is a different bet: that a meaningful slice of app and game discovery will start as a conversational query rather than a store browse. If it pays off, the ranking factors that matter today (store listing optimisation, keyword coverage, screenshot sequencing) will need a Gemini-facing equivalent that nobody has fully mapped yet.

Neither feature has a stated global rollout date. Google attached no install or engagement figures to either at I/O, which is consistent with how it typically ships discovery experiments: broad announcement, narrow initial availability, quiet expansion. The more useful move is to instrument for them now, so that when Sidekick or Gemini discovery reach a meaningful share of a title's Android base there is already a baseline to measure the lift against.

Don't restructure a Q2 plan around either feature this week.

Some context. This is Google's second AI-driven push into the Android funnel this year, after Play's GDC changes in March added an AI overlay called Play Games Sidekick to the roadmap alongside Game Trials and cross-device pricing. I/O has now put a public face and a timeline hint on a product that two months ago was a name on a slide, and the pattern suggests Google is building a layer of AI-mediated discovery and engagement across Play one feature at a time rather than shipping a single big change.

There is also a measurement question worth flagging early, even though Google gave no detail on it at I/O. If discovery genuinely starts moving into Gemini's conversational surface, current attribution setups will struggle: the click-through and view-through paths they expect won't map cleanly onto a query-and-recommendation flow. Nothing about SKAdNetwork or AdAttributionKit changed this quarter, and those are Apple's frameworks in any case, but Play-side attribution teams should ask their MMP now how it would tag a Gemini-originated install, rather than discovering the gap once the feature has real volume behind it.

For a UA team, the sensible response is to treat each announcement as a small, trackable experiment rather than wait for one moment when Android acquisition changes all at once. Assign someone to monitor Sidekick and Gemini discovery rollout by market and by title category, and build the baseline metrics now while both features are still narrow. The moment is more likely to be a slow accumulation of Gemini touchpoints than a single launch day. The teams that benefit will be the ones already measuring before the volume arrived.

Related archive reading

These articles provide related context and remain subject to their stated review status.

• Game Trials, Sidekick and Buy Once, Play Anywhere: Google's GDC changes to the Android funnel
• Android attribution reporting after Sandbox