Android 18 will make contact editing safer for apps

Google is changing how apps add and edit contacts on the upcoming Android release, replacing broad background write access with a more consistent system editor. The change is designed to stop ordinary apps requesting powerful access simply to save one contact.¹

Under the new approach, apps can use the standard ACTION_INSERT, ACTION_EDIT and ACTION_INSERT_OR_EDIT contact intents. Google says these will provide a consistent editor across devices, without requiring direct write permission. Apps that target the upcoming Android release and still try to write contacts directly will face a security exception or permission denial.¹

What is changing

The current WRITE_CONTACTS permission gives an app the ability to add or modify contacts across a device. That can be more access than an app needs, particularly when its real requirement is to let a user create one entry. Google’s proposed editor keeps the action visible to the user and leaves the actual save operation to the system.¹

The new editor can open as a quick half-sheet for a basic entry, then expand into a full-page view for more information. Google’s developer guidance also describes standardised handling for extras such as the account where a contact should be saved and a photo supplied through EXTRA_PHOTO_URI.¹ The company says those details have behaved inconsistently between device makers in the past.

This is not the end of third-party contact managers, diallers or spam blockers. Google says apps that genuinely need broad access will be able to request the new MANAGE_CONTACTS special app access permission, which arrives with Android 17 QPR2 in the fourth quarter of 2026.¹ That access will be controlled through Settings rather than an ordinary permission pop-up, and Google plans Play Console declarations for apps seeking it from 2027 at the earliest.¹

Android Police highlighted the update after Google’s developer announcement, noting that the change is intended to prevent apps from silently adding or altering contacts.² The practical effect is a narrower default: most apps should ask the system to show an editor, while specialist tools will have to justify broader access.

Why it matters

Permissions are only useful when people can understand what they allow. Asking for the ability to rewrite a whole phonebook to save a single contact is a poor fit, even when an app is legitimate. A standard editor gives users a clearer moment of control and should make behaviour more predictable across Android phones.

The rollout will still depend on developers adopting the new intents and device makers implementing the experience consistently. Google’s announcement describes the direction and the compatibility rules; it is not a promise that every existing app will change immediately.

Our opinion

This is a sensible privacy upgrade because it fixes an awkward mismatch rather than simply adding another warning screen. Most apps do not need permanent, silent control of a user’s address book. If Google can make the system editor reliable across manufacturers, asking apps to use it by default should reduce both accidental changes and the damage a malicious app could cause.