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

The foundational shift is designed to curb excessive data access across the Android ecosystem. Historically, applications needing to perform a simple task—such as saving a single phone number or creating a new contact entry—were required to request the sweeping WRITE_CONTACTS permission. While this mechanism technically enabled basic utility, it simultaneously granted apps broad, unchecked authorization to execute widespread modifications to address book data in the background, entirely hidden from the user and executed without active user participation or awareness.

Google officials note that while alternative methods for adding and editing contacts have technically existed for years, developers frequently opted for direct database writes because ecosystem implementations lacked uniformity. In practice, contact intents behaved unpredictably across different device manufacturers and varying OEM skins. Some custom editors routinely dropped critical payloads passed by applications, such as contact photographs. On other devices, unexpected UI behaviors—such as the back button inadvertently saving entries without user intent, or the core "create new contact" option being buried within obscure menus—made asking for blanket permission seem like the only rational choice for developers seeking a reliable experience.

The upcoming Android release aims to resolve these fragmentation issues by forcing devices to adhere to strict, unified standards. Under the new paradigm, applications will leverage standard contact intents, including ACTION_INSERT, ACTION_EDIT, and ACTION_INSERT_OR_EDIT, which will behave consistently across all compliant hardware. When an app invokes these intents, the Android operating system steps in to manage the heavy lifting, presenting a clean, standardized contact editor interface to the user. For new entries, the system opens a streamlined half-sheet form, while updates to existing entries allow users to easily search and append information. Users can seamlessly expand these views into a full-page editor to populate additional details, achieving the desired outcome without the host application ever requiring direct write permissions. Furthermore, developers can streamline the user experience by passing optional data payloads, known as extras, alongside the intent to pre-fill fields such as names, phone numbers, and profile photos.

For developers transitioning away from direct writes, the code refactoring is substantial. Previously, saving a contact required setting up complex content provider operations and applying batches directly to the content resolver, a process entirely dependent on holding the WRITE_CONTACTS permission. Under the new guidelines, developers simply construct an intent with the appropriate action and extras, launching an activity that shifts control to the system UI. Similarly, updating existing records shifts from manual database insertion to launching specific edit actions backed by the target contact’s unique URI.

Beyond general contact intents, Google is introducing specialized pathways for specific use cases. Developers who only require read access to specific contacts chosen by the user are encouraged to utilize the Contact Picker, an API introduced in Android 17 that operates entirely without permissions. Meanwhile, calling and messaging applications that historically injected custom "Call with" or "Message with" rows directly into the user’s address book must transition to a new framework called People Directory, arriving in an upcoming quarterly platform release. People Directory functions as a system-level registry where applications can publish reachability metadata, allowing users to initiate chats and calls from core system apps without polluting or modifying personal contact lists.

Different categories of applications will experience varying impacts from the policy shift. Social networks, peer-to-peer payment platforms, and ride-sharing applications that help users discover friends or split bills will no longer need contact permissions at all, relying instead on the Contact Picker and standard insert actions. Business card scanners and event networking utilities will find that the standardized half-sheet editor perfectly accommodates their workflows, allowing scanned data to be reviewed and saved in a single tap without necessitating background permissions. VoIP and messaging services will substitute direct address book injections with People Directory metadata.

However, a narrow subset of applications requires persistent, broad access to create and modify contacts without continuous user interaction. To accommodate these legitimate use cases, Google is introducing a new special app access permission named MANAGE_CONTACTS, scheduled to arrive with Android 17 QPR2 in the fourth quarter of 2026. This permission is strictly reserved for core utility applications whose primary purpose involves deep contact management, where system intent UIs are entirely impractical.

Determining whether an application qualifies for MANAGE_CONTACTS depends heavily on its core functionality. Applications that simply save contacts from a chat thread, scan business cards, add emails to existing entries, or allow users to pick contacts for payments and sharing do not need the new permission and must continue using standard intents or pickers. Conversely, dedicated contact managers, dialer replacement apps, caller ID and spam protection services that mass-update address book entries, enterprise cloud synchronization tools, bulk backup and restore utilities, device-to-device phone transfer applications, and utilities designed to assign custom ringtones to individual contacts will likely qualify for and require the restricted access.

To implement the special permission where justified, qualifying applications will direct users to a dedicated system settings screen to manually grant access. Google Play will publish updated policy guidelines regarding contact access and the MANAGE_CONTACTS declaration concurrently with the initial ecosystem rollouts.

The implementation timeline spans several phases to give developers ample time to adapt their codebases. On October 21, 2026, Google Play formally announced the upcoming MANAGE_CONTACTS policy. Later that year, the permission becomes available with Android 17 QPR2. In 2027, the core enforcement arrives with the upcoming Android release, at which point WRITE_CONTACTS will cease granting write access to targeting applications, and contact intents will achieve mandatory cross-device consistency. Following that release, the Google Play Console will begin requiring apps utilizing MANAGE_CONTACTS to submit formal policy declarations and undergo compliance checks.