Play policies are turning into product work (contacts picker, location button, and account transfers)

Original article (source): Android Developers Blog - “Boosting user privacy and business protection with updated Play policies” (Apr 15, 2026)

• https://android-developers.googleblog.com/2026/04/giving-users-clearer-choice-and-everyone-a-safer-more-trusted-app-ecosystem.html

The real takeaway

Google is not just updating policy language. They are shipping opinionated UX primitives (like the Contact Picker and the location button), then nudging policy and tooling (Android Studio insights, Play Console pre-checks) to make those primitives the default.

If you ship an app with broad permissions “because it’s easier”, you are moving against the grain.

1) Contact Picker: “invite friends” without taking the whole address book

The post positions the Android Contact Picker as the new standard for contact access. It is explicitly meant for:

• invites,
• sharing,
• one-off lookups.

And it sets expectations that READ_CONTACTS should be rare.

Practical implication:

• most consumer apps should migrate to the picker (or Sharesheet) and delete READ_CONTACTS.

2) Location button: one-time precise location without the full permission dance

For apps that need precise location for a discrete action (find a store, tag a photo), Android is introducing a location button designed to reduce user confusion and friction.

Practical implication:

• if your location use is “one-and-done”, you should adopt the button and avoid training users to reject permissions on day 0.

3) Account Transfer: ownership changes must go through the official workflow

Google is also tightening up account security by requiring ownership transfers to use the official Play Console workflow (with a mandatory cool-down period).

Practical implication:

• treat account ownership changes as an operational project, not an admin task. There is now a formal process and timing involved.

Tiny win

Make a short spreadsheet with three columns:

• Permission or capability (contacts, location, account admin)
• The user action that genuinely requires it
• The narrowest compliant mechanism (picker/button/official workflow)

Then pick one migration to ship this sprint. Policy compliance is now a compounding advantage, because it reduces review surprises and user distrust at the same time.

Read the original: https://android-developers.googleblog.com/2026/04/giving-users-clearer-choice-and-everyone-a-safer-more-trusted-app-ecosystem.html