A more reliable way to add and edit contacts on Android | Android Developers’ Blog

Under the new policy framework, apps targeting the upcoming Android release that attempt to write directly to device contacts will face immediate rejection, triggering a SecurityException or outright permission denial. For years, the WRITE_CONTACTS permission has acted as a broad key to the kingdom, allowing applications to modify, create, and delete contact entries across a device in the background without requiring active user engagement or awareness. Industry observers and privacy advocates have long noted that this wide-reaching access model was overly permissive, particularly given that the vast majority of mobile applications only need to save a single contact or update a piece of information on behalf of the user.

To bridge the gap and provide a secure alternative, Google is standardizing standard contact intents—specifically ACTION_INSERT, ACTION_EDIT, and ACTION_INSERT_OR_EDIT—across the entire Android ecosystem. In previous versions of the operating system, relying on these intents presented fragmentation challenges for developers. Behavior varied unpredictably from one device manufacturer to another. Certain custom editors would inadvertently drop passed data payloads like contact photos, while other devices suffered from confusing navigation where the physical back button might accidentally save an unintended contact or bury the creation options altogether.

The upcoming Android release addresses these legacy inconsistencies by enforcing strict behavioral standards across all participating hardware. When apps invoke these system intents, the operating system takes over the heavy lifting, presenting users with a clean, standardized contact editor experience. For new entries, the system opens a quick, intuitive half-sheet form. For existing records, users can seamlessly search and append information or expand the interface into a full-page editor to fill out more comprehensive details. Critically, this entire workflow happens without the host application ever requiring direct write permissions to the user’s address book.

Developers can further optimize this interaction by passing optional data payloads, known as extras, alongside their intents. For example, creating a new contact can now seamlessly pre-fill names, phone numbers, designated destination accounts, and contact photos through parameters like EXTRA_PHOTO_URI. This transition shifts the responsibility of modifying sensitive data away from background processes and places it firmly under the direct supervision of the device user, who can verify and approve every addition with a single tap.

Beyond the standard contact intents, Google is expanding the platform’s architectural toolkit to accommodate specialized application categories. For developers building calling, messaging, social, or peer-to-peer payment utilities, the need to inject custom rows directly into a user’s address book is being phased out in favor of alternative system mechanisms. Applications that previously relied on WRITE_CONTACTS merely to display "Call with" or "Message with" shortcuts inside the native contacts app will transition to the People Directory. Set to arrive in Android 17 QPR2 in the fourth quarter of 2026, the People Directory functions as a dedicated system registry where apps can publish reachability metadata, enabling communication features without tampering with local address book entries. Similarly, applications requiring temporary, one-time access to read specific contacts can utilize the Contact Picker, which operates entirely without permissions.

Despite the widespread shift toward intent-based interactions, Google recognizes that certain classes of applications require continuous, broad access to create and modify contacts as part of their core functionality. For these select use cases, a new special app access permission named MANAGE_CONTACTS is being introduced in Android 17 QPR2, with Google Play publishing updated compliance guidelines.

The MANAGE_CONTACTS permission is strictly reserved for software whose primary purpose revolves around address book management and synchronization. Eligible categories include dedicated contact managers, dialer replacement apps, caller ID and spam protection utilities that perform mass updates to address book entries, and enterprise or cloud synchronization tools that execute continuous, two-way background backups without user intervention during every transaction. Bulk device-to-device transfer tools and applications that assign custom ringtones to individual contacts will also likely qualify for the special access tier.

Conversely, everyday consumer applications—such as social networks, ride-sharing platforms, business card scanners, and messaging clients—do not qualify for MANAGE_CONTACTS. These apps are expected to rely on the standard contact intents, the Contact Picker, or the People Directory. Having a custom-branded user interface for editing contacts inside an app does not exempt developers from these new rules, nor does it qualify them for the special permission.

The rollout of these changes follows a structured timeline. Google Play announced the formal policy guidelines for MANAGE_CONTACTS on October 21, 2026. The permission itself will become available with the release of Android 17 QPR2 later that year. Enforcement will tighten significantly with the subsequent Android release in 2027, at which point the traditional WRITE_CONTACTS permission will officially cease to grant write access for targeted applications, and contact intents will be fully standardized across all compliant devices. Concurrently, the Play Console will introduce declaration requirements for applications utilizing the MANAGE_CONTACTS permission to ensure rigorous oversight of high-privilege access across the ecosystem.