Act this weekWhat happenedGoogle announced that apps targeting the next Android release can no longer write to contacts directly and must use standard contact screens instead.
Who is affectedAndroid app developers, and businesses with apps that save contacts, such as CRM, dialer, messaging and booking apps.
What to do- 1Check whether your app asks for the WRITE_CONTACTS permission.
- 2Switch to the ACTION_INSERT, ACTION_EDIT or ACTION_INSERT_OR_EDIT contact intents.
- 3Apply for MANAGE_CONTACTS only if your app truly needs broad contact access.
- 4Read the updated Google Play contact access guidelines before you update your app.
Android apps are about to lose a quiet power: saving or changing your contacts without asking. Google announced that apps built for the upcoming Android release can no longer write to contacts directly. Instead, they must open a standard contact screen, so you see each change before it is saved.
What changed
Until now, an app that wanted to save even one contact could ask for a permission called WRITE_CONTACTS. Google says that permission is broad. It lets an app make widespread changes to contacts across the device, in the background, even without any action from you. Most apps do not need that much.
Under the new rule, apps that target the upcoming release will have those direct writes rejected. They will use three standard contact actions instead, called ACTION_INSERT, ACTION_EDIT and ACTION_INSERT_OR_EDIT. These need no permission at all.
What you will see
For a new contact, the system shows a quick half-sheet form. To update someone already in your address book, you search for the contact and add the new details. You can expand either one into a full-page editor. Google notes that phone makers may change the look to match their own software, but the behavior will stay the same.
Google shared early mockups and labeled them not final, so the exact design may still change.
Why the old way stuck around
Google admits the standard screens were part of the problem. They used to behave differently from phone to phone. Some editors dropped details an app passed in, such as a contact photo. On some devices the back button saved a contact when the user did not mean to. In others, the option to create a new contact was hard to find. Asking for the broad permission was the easier choice for developers.
Google says it is fixing these issues in the upcoming version and requiring devices that run it to follow the same standards. Apps will also be able to pre-fill a contact photo.
Who it affects
Everyday users do not need to do anything. The change is meant to protect your address book. Developers and businesses are the ones with work to do. That includes makers of customer management, dialer, messaging and booking apps that save contacts.
A small group of apps that truly need broad access to create and edit contacts can use a new permission, MANAGE_CONTACTS. It arrives in Android 17 QPR2, due in the fourth quarter of 2026. Google Play published updated contact access guidelines, including this permission, on the day of the announcement.
What to do
If you run a business with an Android app, ask your developer whether it uses WRITE_CONTACTS. The steps in the alert box above cover the switch and the new permission.
What happens next
The material does not give a release date for the upcoming Android version. It also does not say how many apps will qualify for MANAGE_CONTACTS. Watch for the final editor design and for Google Play's contact access guidelines, which now apply to any app that wants broad access.
The takeawayIf your Android app saves contacts, check for WRITE_CONTACTS now and plan to move to the standard contact screens.