Android removes direct writes to contacts: app developers are required to use standard intents
Public- 21 Oct, 2026

Starting with the upcoming Android release, applications that target this new version will lose the ability to write directly to the device contact list using the WRITE_CONTACTS permission. Any attempt to perform direct writes via ContentProvider operations or similar mechanisms will result in a SecurityException or permission denial. To ensure privacy and consistency, developers are required to migrate to standard contact intents: ACTION_INSERT, ACTION_EDIT, and ACTION_INSERT_OR_EDIT. These intents do not require any special permissions and are designed to handle the creation and modification of contacts through a system-managed interface, ensuring that user data is handled securely and transparently.
Previously, the behavior of these contact intents varied significantly across different device manufacturers, leading to inconsistent user experiences such as lost data or unexpected saving behaviors. The upcoming Android version standardizes this experience, requiring all devices to follow strict guidelines. When an app triggers these intents, the system presents a clean, half-sheet form for new entries or allows users to search and update existing contacts. Users can expand this into a full-page editor for detailed information. This standardized approach eliminates the need for broad permissions for most apps, as the system handles the data entry directly, reducing the attack surface and improving user trust in contact management.
For the small subset of applications whose core functionality involves managing contacts, a new special app access permission called MANAGE_CONTACTS will be introduced in Android 17 QPR2, scheduled for Q4 2026. This permission grants broad access to read, add, edit, and delete contacts, accounts, and People Directory data, effectively replacing the need for both WRITE_CONTACTS and READ_CONTACTS in qualifying scenarios. Apps seeking this permission must submit a declaration in the Play Console explaining why standard intents are insufficient for their core functionality. This measure ensures that only applications with a genuine need for broad contact access can bypass the standardized intent-based workflow.
Developers should also consider the new People Directory feature, arriving in the same release, which allows apps to publish contact reachability information without directly editing user contacts. This is particularly relevant for apps that previously added "Call with" or "Message with" actions by writing extra entries to the contact database. By using People Directory, apps can maintain these features without violating the new restrictions on direct contact modifications. This shift encourages a more modular approach to contact integration, where apps contribute to the directory rather than altering the user's personal contact list, thereby preserving the integrity of the user's data while still providing useful connectivity options.
The migration process involves identifying all direct contact writes in the codebase, such as those using ContactsContract.RawContacts.CONTENT_URI or applyBatch methods, and replacing them with the appropriate intents. Developers should use ACTION_INSERT for new contacts and ACTION_EDIT or ACTION_INSERT_OR_EDIT for updates, passing optional data payloads like names, phone numbers, and photos via Intent Extras. For reading contacts, the Contact Picker, available since Android 17, remains the recommended solution, requiring no permissions. Apps targeting older Android versions will retain their current behavior, but the new standardized editor will be available to all apps on the new OS, ensuring a consistent experience for users regardless of the app's target SDK.