Updated Play policies: Contact Picker, location button, and account transfer workflow (Android Developers Blog)

Google’s Android Developers Blog posted a companion explanation of the April 2026 Play policy updates, with a more “here is what to build” angle. It is essentially Google saying: use the safer primitives, reduce permission friction, and stop doing sketchy account transfers.

• Source: Android Developers Blog, “Boosting user privacy and business protection with updated Play policies”
• Read: https://android-developers.googleblog.com/2026/04/giving-users-clearer-choice-and-everyone-a-safer-more-trusted-app-ecosystem.html

The one-line lesson

Permission UX is now part of the release pipeline, so the lowest-friction, lowest-scope implementation wins.

What stood out

• Contact Picker is the new baseline for invites and sharing. If your use case is “pick a couple of people to invite”, broad READ_CONTACTS access looks increasingly indefensible.
• The location button reframes precise location as a one-time action, not a forever permission. If you only need location for a single task, Google wants the request to feel temporary and obvious.
• Account transfer is now an official workflow with a cool-down period. That is a product and ops change, not just legal paperwork.
• Tooling is coming to catch you earlier. They call out future checks in Android Studio and pre-review checks in Play Console to flag contacts and location issues before submission.

Why this matters (practically)

This is not “policy talk”, it is a roadmap for what review teams will expect:

• fewer broad sensitive permissions
• more user choice inside the moment of use
• clearer paper trails for account ownership

Tiny win (20 minutes)

Pull your AndroidManifest.xml and answer two questions:

1. which features truly require broad contacts or always-on precise location?
2. which ones are just convenience, and can move to Contact Picker or a one-time location flow?

If you cannot explain it in plain English, reviewers will not like it either.