Google is changing how Android apps add and edit contacts, moving away from the broad WRITE_CONTACTS permission toward standardized system editors that let users review and save contact information themselves. The change, announced on October 21, is intended to reduce unnecessary access to address books while making contact-editing behavior more consistent across Android devices.

Under the upcoming Android release, apps targeting that version will no longer be able to write directly to contacts using WRITE_CONTACTS. Instead, developers will need to use Android’s standard contact intents for user-driven changes, with a new MANAGE_CONTACTS special app access permission reserved for applications that genuinely need broader contact-management capabilities.

How Android’s new contact-editing system works

Google says the existing WRITE_CONTACTS permission gives apps broad access to modify a user’s contacts, including making changes in the background without direct user interaction. However, many apps only need to save a contact when someone taps a button, such as adding a person from a messaging conversation, saving a business card, or storing a phone number from a profile.

To handle those situations, Android is standardizing three existing intents: ACTION_INSERT, ACTION_EDIT, and ACTION_INSERT_OR_EDIT. These allow apps to open the system’s contact editor instead of directly modifying the address book.

The new experience includes a compact, half-sheet editor for creating contacts, along with an option to expand the interface into a full-page editor for additional details. When adding information to an existing contact, users can search for the relevant entry and review the proposed changes before saving them.

Google says device manufacturers may adapt the interface to match their own software designs, but the underlying behavior will remain consistent across supported devices. The interface shown in Google’s announcement is still marked as a work in progress.

The standardized editor will also support prefilled information to make the process quicker. Developers can use EXTRA_ACCOUNT to suggest which account should store a contact, while the upcoming Android release will introduce standardized support for EXTRA_PHOTO_URI to prefill a contact’s photo.

Which apps will need to change?

The transition primarily affects apps that currently write contact information directly when a user initiates an action.

Social networks, payment services, ride-sharing apps, business card scanners, and event networking apps can use the system editor to let users save contact details without granting the app broad write access. Apps that need to let users select existing contacts for invitations, payments, or sharing can use Android’s Contact Picker, introduced in Android 17, which does not require a contacts permission.

Calling and messaging apps have another option. Rather than inserting custom call or message actions directly into a user’s address book, they can use People Directory, a new system directory scheduled to arrive with Android 17 Quarterly Platform Release 2 (QPR2) in the fourth quarter of 2026. It will let apps publish information about how people can reach users within their services without modifying the user’s contacts.

There is an important exception for applications that genuinely need to manage contacts directly. Dedicated contact managers, dialer replacements, certain caller ID and spam-protection apps, and services that perform bulk contact backups or continuous cloud synchronization may qualify for the new MANAGE_CONTACTS permission.

Google says a custom-branded contact editor alone will not qualify an app for this permission. Developers distributing apps through Google Play will also need to submit a declaration explaining why the standard contact intents are insufficient for their app’s core functionality.

When will the change take effect?

The rollout will happen in stages rather than immediately breaking existing Android apps.

Google Play announced its updated contact-access policy on October 21, 2026. The new MANAGE_CONTACTS permission is scheduled to become available with Android 17 QPR2 in the fourth quarter of 2026.

The main WRITE_CONTACTS change is planned for the upcoming Android release in 2027. Once an app targets that release, direct contact writes without MANAGE_CONTACTS will be rejected, potentially resulting in a SecurityException or permission denial.

Apps targeting older Android versions will retain their existing behavior. However, the standardized contact editor will be available on devices running the new Android release, regardless of an app’s target SDK.

Google recommends that developers audit their code for direct contact-writing operations, migrate user-initiated changes to the appropriate intents, and remove WRITE_CONTACTS from their app manifests once it is no longer needed.

For most apps, the change should mean fewer permissions to request and less responsibility for building and maintaining contact-editing interfaces. For users, it puts the system’s contact editor back in control of changes that would otherwise happen directly in their address books.