Android 17 is stable on Pixel devices as of mid-2026, and its headline changes aren’t visual — they’re structural changes to how apps are allowed to hold onto user data. The new Contacts Picker grants temporary, field-level access to only the specific contact data an app requests, rather than the broad READ_CONTACTS permission apps have relied on for over a decade. A parallel session-based location button gives apps precise location for the current session only, closing when the app does, instead of a standing grant that persists until the user manually revokes it.
Both changes follow the same logic Apple has been pushing on iOS for several release cycles: permissions as a rolling negotiation rather than a one-time toggle. For teams commissioning an app, that’s not a footnote — it’s a design constraint. Any feature that assumed persistent background access to contacts or location (contact sync, geofencing, location-based notifications when the app isn’t open) needs an explicit re-request flow built in, and that flow needs to degrade gracefully rather than nag the user every session. Google has also added a Handoff API letting apps specify state to resume across a user’s other devices, which raises the same question in reverse — what state is worth persisting across devices now that per-app data access is more tightly scoped.
None of this is a reason to delay an Android build. It’s a reason to make sure whoever specs the app has actually read the platform’s current permission model rather than designing against how Android worked two or three years ago, because the difference shows up in App Store review, user trust, and how much re-engineering a “just add background location” feature request costs later.
So what
If you’re commissioning an Android app — or maintaining one that leans on contacts or location — treat platform permission changes like this as a spec input, not a launch-week surprise to patch around. Our iOS & Android development work builds against current platform requirements from day one; get in touch if you want a permissions and data-handling review before you scope a build.