Android
Mobilsfera Newsroom
Android

Google Play's new permission rules are good, but unproven

Making developers justify broad location, contacts and local-network access is overdue. It only matters if Google enforces it visibly and users can see the answers.

Published
November 18, 2026
Reading time
3 min
Categories
Android

AI-generated image

Does a flashlight app, or a pizza app, really need to know where you are all day and who is in your address book? For years the honest answer was no, and the permission prompt was often the only thing standing in the way. Google Play is now asking developers to explain themselves. We think that is the right move, and we also think it will mean little until we see it enforced.

As Clubic reports, from January 27, 2027, apps on Google Play that target Android 17 (API 37) or later and only need a precise location now and then must use the system location button. It limits access to the current session. Apps that keep requesting ACCESS_FINE_LOCATION, such as navigation apps, must justify in the Play Console why approximate location and the button aren't enough.

The same day, apps requesting READ_CONTACTS must show that the Android contact picker is insufficient. Later dates follow. Local-network access needs a justification from August 25, 2027, and Google's policy announcement of October 29, 2026 already confirms the location rules.

The design is right: the default is "less"

The best part is the direction of the burden. Until now, users had to judge whether an app deserved a broad permission. Now the developer has to argue first, and the narrow option, whether button or picker, becomes the normal path. Inviting a friend shouldn't hand over your whole contact list. That is a simple principle, and Android took a long time to make it the default.

It also helps that Google isn't banning anything. A navigation app really does need continuous precise location. A policy that asks "why isn't the narrow tool enough?" is more realistic than a blanket ban, and harder for honest developers to resent.

But a declaration form is not protection

Here is our reservation. A justification in the Play Console is a text box that a reviewer reads. Clubic notes that Google will examine it, and one Google support page says apps in scope are subject to enforcement after the date if they are not compliant. That is a promise. We have no evidence yet of how strict reviews will be, how many apps will be rejected, or what happens to existing apps that never update their target version.

That last point matters. These rules apply to apps targeting Android 17 or later. Our reading, and it is an inference, is that older-targeting apps keep their habits until their developers move. So the practical effect will arrive gradually, not in January.

Show users the answers

If we could change one thing, it would be visibility. A justification only the developer and Google can read protects no one directly. If a short, plain-language summary of "why this app needs your precise location all the time" appeared in the store listing or in the permission dialog, the policy would also put pressure on developers through reputation. Without it, users are asked to trust a process they cannot see.

Verdict

Welcome and overdue, yes. A reason to relax, not yet. Until Google publishes enforcement results or shows users these declarations, treat the new rules as a promise. In the meantime, choose "approximate" or "only while using the app" whenever an app lets you, and be suspicious of any app that insists otherwise. The update will help, but your own permission settings remain the more reliable protection.

Debate topics

No topics yet: start the first one.

More stories