The Android 17 location button and Google Play’s precise location rules
Short answer: for apps targeting Android 17 (API level 37), Google Play makes the Android location button the required way to get precise location for one-time tasks such as search nearby, sharing where you are or filling an address. It grants precise location for one session only. Every app requesting ACCESS_FINE_LOCATION must justify it in a Play Console declaration, available from November 2026, and compliance is mandatory from January 27, 2027, with 30-day self extensions in Play Console.
Coarse location, location button or precise permission?
From Google’s Minimum Scope location policy, read 1 October 2026. Examples are Google’s and not exhaustive.
| What your feature does | Google’s minimum scope | Example |
|---|---|---|
| Needs only a city or region | ACCESS_COARSE_LOCATION | Local news, regional weather, nearest branches within 10 miles |
| Needs a precise point once | Location button | Search nearby, share location once, tag a post, address picker |
| Tracks location continuously in the app | ACCESS_FINE_LOCATION with declaration | Run tracking, turn-by-turn navigation |
| Acts when entering or leaving an area | ACCESS_FINE_LOCATION with declaration | Reminder when arriving at a store |
| Needs location while not visible | Background location review | Not covered by the button |
How the location button works
It is a system UI element the user taps to share precise location for the current session; access ends when the session closes. You add it with a Jetpack library, currently marked experimental, and declare the standard location permissions plus USE_LOCATION_BUTTON. You can change colors, outline, size, shape and pick the label from a predefined list such as “Use precise location”, but the location icon is mandatory and the font size is managed by the system. On Android 16 and lower the library shows the same button and falls back to the standard permission prompt, so you need no separate path.
Declaring button-only precise location
If your app needs precise location only through the button, declare it in the manifest with the onlyForLocationButton flag on ACCESS_FINE_LOCATION. Google’s next steps: audit whether your app targets Android 17 and uses precise location for one-time tasks, add the flag, and check that the button follows Android design guidelines.
Keeping ACCESS_FINE_LOCATION
Persistent precise location stays allowed when it is essential to the app’s main purpose or a major feature promoted in your store listing, such as live tracking or navigation. In the declaration you pick the user-facing features that need it, for example search nearby, live tracking, navigation, geofencing, automated tagging, nearby devices on Android 11 and lower, browser location or network diagnostics, and explain why coarse location or the button is not enough. Location may never be requested only for ads or analytics, and location data may never be sold. Existing apps are not exempt: updates that don’t comply may be rejected.
Other changes on the same date
January 27, 2027 also enforces the contacts rules, see Android Contact Picker and READ_CONTACTS, and removes geofencing as a foreground service use case. The full list is in Google Play policy updates 2026, and target SDK dates are in Google Play target API level.
Where Censuus fits
Asking for less keeps installs coming; being found brings them in the first place. Censuus ranks apps by the visits they draw, and adding your app is free on the List my app form. Placement comes from traffic and sponsorship: apps climb on the visits they draw, and a sponsor can pay to rise higher.
Frequently asked questions
What is the Android location button?
A system button, added with a Jetpack library, that gives an app precise location for the current session after the user taps it, instead of a runtime permission prompt.
When is the location button required on Google Play?
For apps targeting Android 17 (API level 37) and higher that need precise location only for one-time tasks. Compliance is mandatory from January 27, 2027.
Do I need a declaration for ACCESS_FINE_LOCATION?
Yes. All apps requesting precise location must complete a Play Console declaration, available from November 2026, explaining why the location button or coarse location is not sufficient.
Does the location button work in the background?
No. It is only for foreground, one-time use; background location follows its own review.
What happens on Android 16 and lower?
The Jetpack library shows the same styled button but triggers the standard location permission prompt.
Guides for app developers
- Phone verification without READ_CALL_LOG: what replaces call-based checks
- Android Contact Picker and the new READ_CONTACTS rules
- Google Play policy updates in 2026, with the deadlines
- Google Play target API level requirements for 2026
- The Android 17 local network permission
- Android 17 behavior changes: a checklist for target SDK 37
Put your app in the ranking
Censuus ranks apps by the visits they draw and by sponsorship, no bots. Listing is free; sponsorship raises placement.