Apps & Software

Android Updates Contact Permissions for Upcoming Release

Google outlines major updates to contact management on Android, removing direct write access for apps targeting upcoming releases in favor of standardized intents.

Radwan AbdulhadiEditor and technology writer

Published: October 21, 2026 · Updated: October 21, 2026 · 3 min read

Android Updates Contact Permissions for Upcoming Release — Image: Android Developers

Changes to Contact Write Permissions

According to the Android Developers' Blog, applications targeting the upcoming Android release will no longer have the ability to directly write to contacts using the traditional WRITE_CONTACTS permission. Instead, developers are being guided to shift their approach and utilize standard contact intents for managing user information.

If an app targets the upcoming release or later and attempts to write to contacts directly, those write requests will be rejected. This action results in a SecurityException or a permission denial. Historically, requesting WRITE_CONTACTS granted broad access, permitting applications to make widespread changes to device contacts in the background without user interaction. Most applications do not require this level of broad access.

Standardized Contact Intents and Editor Experience

To replace direct writes, developers can implement standard contact intents including ACTION_INSERT, ACTION_EDIT, and ACTION_INSERT_OR_EDIT. For comprehensive guidance, a developer guide is available on how to modify contacts using intents to ensure proper implementation.

Previously, contact intents behaved inconsistently across different devices from various manufacturers. Some editors dropped passed data such as contact photos, while other devices triggered accidental saves via the back button. The upcoming Android version addresses these issues by requiring devices running the OS to follow unified standards, ensuring consistent behavior across the entire ecosystem without requiring any special permissions.

Image related to the report from Android Developers · Source: Android Developers

System-Handled Editor and Optional Extras

When utilizing intents such as ACTION_EDIT or ACTION_INSERT_OR_EDIT, the operating system handles the workload by presenting a standardized contact editor experience. The interface opens a quick half-sheet form for new entries or allows users to search and add information to existing contacts seamlessly, all without requiring direct write permissions from the host application.

Developers can further optimize the contact creation process by passing optional data payloads known as Extras alongside the intent. The EXTRA_ACCOUNT extra suggests the target account for saving, while the EXTRA_PHOTO_URI extra passes a photo to pre-fill the contact picture, with the system editor managing the URI read permission automatically.

Introduction of MANAGE_CONTACTS Permission

For a small subset of applications requiring broad access to create, modify, or delete contacts, a special app access permission called MANAGE_CONTACTS arrives in Android 17 QPR2, scheduled for the fourth quarter of 2026. Google Play is publishing updated guidelines regarding contact access and this new permission.

MANAGE_CONTACTS is designed as a special app access permission rather than a runtime dialog, requiring users to manually enable it under device settings. Applications utilizing this permission must submit a declaration in the Google Play Console explaining why standard intents are insufficient for their core functionality.

Image related to the report from Android Developers · Source: Android Developers

Alternative Solutions for Specialized Actions

For apps that only need to read contacts chosen directly by the user, the Contact Picker offers an alternative that has been available since Android 17 and requires no permissions at all.

Similarly, applications that currently add calling or messaging shortcuts to device contacts by writing extra entries can transition to the People Directory. Scheduled to arrive in Android QPR2 in late 2026, this new system directory allows apps to publish communication options without editing the user's personal contacts.

Figure02_01_Add_To_Existing_0_Search_State_Half_Sheet.png — Image related to the report from Android Developers · Source: Android Developers

Developer Migration Steps

Developers preparing for the upcoming changes should audit their codebases to find existing contact writes by searching for WRITE_CONTACTS and related content URIs. Code paths should be updated to replace user-driven writes with standard intents, utilize standard data types, and remove the WRITE_CONTACTS manifest entry once code paths no longer require it.