Android 17’s Contact Picker: a privacy-first replacement for broad contacts permission

Original post (source): Android Developers Blog - “Contact Picker: Privacy-First Contact Sharing”

• https://android-developers.googleblog.com/2026/03/contact-picker-privacy-first-contact.html

What changed

Android is positioning the Android Contact Picker (introduced in Android 17) as the new default for contact selection.

The core idea: instead of asking for broad READ_CONTACTS access (which often grants far more than an app needs), the picker allows users to share only the specific contacts they choose.

How it works (developer-level)

The post highlights using the Intent.ACTION_PICK_CONTACTS intent, and calls out capabilities including:

• Granular data requests (e.g., ask for emails or phone numbers rather than whole contact records)
• Single or multi-select
• Selection limits
• A session URI that provides temporary read access to the requested data
• Access across profiles (e.g., work profile) where applicable

Why this matters for app and growth teams

Contacts permissions are one of the fastest ways to create:

• onboarding drop-off (users say “nope”),
• review/policy friction,
• and distrust that bleeds into ratings.

If your “invite friends” or “share with contacts” flow is optional, switching to a picker is a clean way to reduce permission anxiety while still enabling the feature.

Tiny win (practical follow-up)

Find one place you ask for contacts access and rewrite it to be picker-first:

• Don’t ask for broad access at app start.
• Trigger the picker only when the user taps an explicit “Invite” or “Share” action.

Then measure: invite-start rate, invite-complete rate, and any change in onboarding completion.

Read the original: https://android-developers.googleblog.com/2026/03/contact-picker-privacy-first-contact.html