Android Developers: Play is pushing contact picker, location button, and a real account transfer flow

Summary

Google’s Android Developers blog post (April 2026) is the “why” behind the Play policy announcement: reduce broad permission scope, make one-off access easier, and close the door on sketchy account transfers.

Three concrete changes to pay attention to:

• Contact Picker becomes the default for common “invite/share/lookup” use cases (with READ_CONTACTS reserved for apps that genuinely cannot function without it).
• A streamlined location button is positioned as the preferred way to request precise location for one-time actions.
• Official account transfer in Play Console becomes mandatory for ownership changes, with a security cooldown.

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

What’s actually changing

1) Contact access: Picker first (and Sharesheet where it fits)

Google points to using:

• Android Contact Picker, and
• Sharesheet,

…as privacy-focused alternatives, with READ_CONTACTS reserved for apps that need broad ongoing access.

If your app asks for contacts just to:

• invite friends,
• share something,
• do a one-time lookup,

…this is the nudge to redesign.

2) Location: “location button” for one-off precise actions

Google’s framing is explicit: if you need precise location for a discrete action (find a store, tag a photo), use the button rather than leaning on traditional permission flows.

Practical implication: this is a UX move as much as a policy move. It should reduce friction, but only if your flow is already scoped to one-off access.

3) Account transfer: business protection (and no more credential sharing)

Google says the official transfer feature is designed for sales/mergers, and that unofficial transfers (credential sharing, third-party marketplaces) are not permitted.

Notable operational detail:

• a mandatory 7-day security cool-down for transfers.

If you ever acquire apps, treat this as timeline impact, not just admin paperwork.

What’s next (important dates)

The post calls out:

• Play policy insights in Android Studio coming later in the year.
• Pre-review checks in Play Console planned for October (to flag contact/location policy issues before submission).

What to do this week (tiny wins)

1. Audit your permission “story” For contacts/location, write a single sentence per request: “We ask because…”. If you can’t defend it, redesign it.

2. Prototype a picker-based flow Pick your highest-volume contacts use case (invites), and build the picker path first.

3. Write an account transfer runbook Even if you don’t plan to transfer accounts, document the approved path now. It’s cheaper than learning it mid-deal.

Category tag

Policy & Permissions

Internal links

• Retention marketing guide: /guides/retention-marketing-guide/
• Measurement and attribution guide: /guides/measurement-and-attribution-guide/

Editor: App Store Marketing Editorial Team