google i/o 2026 is 16 days out — a small indie's pre-show checklist

google i/o 2026 starts may 19, the android show drops may 12, and android 17 stable lands sometime in june. that's a 60-day window where every play store submission decision you make either rides the wave or eats the wake.

most indie devs will spend the next two weeks reading speculation about gemini features they'll never integrate. the smarter move is boring: line up your release so it's already android-17-ready the day the keynote ends.

what's actually shipping#

android 17 hit beta 4 on april 16 — the last beta before stable. the headline dev-facing changes are the photo picker grid customization (you can finally render 9:16 portrait thumbnails), ACTION_PICK_CONTACTS for session-based field access without full READ_CONTACTS, and ImageFormat.RAW14 for pro camera apps. on the policy side, the contacts permissions tightening is the one that quietly sinks update submissions if you haven't migrated.

google has also moved away from the old developer preview cadence — canary builds now run year-round, so the surprise-deadline pattern devs got used to in the android 14/15 era is mostly gone. that's good news. the bad news is the policy reviewers don't care that the canary cycle is "softer" — they still flag old contact permission patterns on first submit after the api 36 cutover.

the two-week checklist#

if you only do four things between now and may 19:

1. bump compileSdk to 36 and run the lint pass. most indie apps i've seen take less than a day. the app actually breaking is rare — the broken thing is usually a third-party sdk that hasn't updated.
2. audit your contacts and photo picker code. if you're still requesting READ_CONTACTS for a one-shot picker flow, switch to the system intent now. reviewers are flagging this aggressively.
3. regenerate your screenshots for android 17 device frames. the new bubble bar and updated system chrome show up in screenshots taken after a target-sdk bump, and play store rejects mismatched frames more often than people realize.
4. draft a "what's new in this version" line that doesn't mention android 17 by name. play store's editorial team is more likely to surface releases that feel current without being version-chasing.

that's it. don't try to ship a gemini integration in two weeks because the keynote name-drops it. ship the boring update, then iterate.

the stora angle#

this is the kind of release where the actual code changes are small and the submission surface area is what eats the week. screenshots in the new device frames, a compliance pre-check on the contacts/permissions changes, an updated store listing in 30+ locales — that's two days of fiddly work for a solo dev.

stora's screenshot generator handles the device frame swap automatically when you bump targetSdk, and the compliance engine flags the contacts/permission patterns reviewers are catching right now, before you submit. the point isn't to ship faster for its own sake — it's to make the boring part take an hour so you have time left to actually watch the keynote.

i/o is in 16 days. ship the update on may 18. then enjoy the show.