Android Location Precision (None / Approximate / Precise)
This feature was shipped May 2026 in response to Google Play Developer Program Policy update on precise-location permissions.
What this setting controls
Android apps must declare what kind of location data they collect. Adalo gives you three tiers in Publish βΊ Android Settings βΊ App Settings βΊ Location Precision:
None β your app does not request location at all. Any location features (Maps, distance sort, "Current Location" magic text, Location Input default, Request Location Permission action) will be blocked on Android.
Approximate (default for new apps) β your app gets the user's general area, accurate to roughly a city block or neighborhood. Good for "near me" lists, city-level filtering, and most map use cases that don't need a precise marker.
Precise β your app gets the user's exact coordinates with high accuracy. Required for exact "you are here" pins, geofencing within a few meters, or anything that depends on real-time GPS.
Please Note: Adalo does not currently support turn-by-turn directions. This list reflects Android use cases that require Precise location in general, not features Adalo offers out of the box.
iOS uses its own location model and is not affected by this setting.
Which tier do I need?
No location features at all
None
Sorts or filters lists by distance ("show me restaurants within 10 miles")
Approximate
Uses Current Device Location magic text for city, zip, or general area
Approximate
Shows a map centered roughly where the user is
Approximate
Shows the user's exact position as a moving marker on a map. (May require custom component)
Precise
Tracks a delivery, ride, or route in real time. (Not currently possible in Adalo)
Precise
Needs accurate distance under ~100 meters
Precise
HINT: When in doubt, start with Approximate. You can switch to Precise later and rebuild if you find your feature needs more accuracy.
How to change the setting
1.) Open your app and click Publish in the top-right corner.
2.) Choose the Android tab.
3.) Click App Settings.
4.) Under Location Precision, choose None, Approximate, or Precise.
5.) Click Save.
6.) Rebuild your Android AAB and resubmit it to the Google Play Store for the change to reach your published app. Apps already live on the Play Store keep their previous permissions until you rebuild.
Why Precise needs extra care
Google Play reviews apps that declare precise location (ACCESS_FINE_LOCATION) more strictly. Per Google's policy, you should only request precise location when your app's core feature genuinely needs it, and you should be ready to explain that need during Play Store review. Apps that declare Precise without a clear use case may face review pushback or rejection.
Read Google's policy directly: Location permissions on Google Play.
NOTE: Adalo will warn you in the builder when you select Precise. The warning is a heads-up, not a block. You can still publish, but be ready to justify the choice if Google asks.
What happens to my existing app?
If your app was published before the Location Precision setting existed, Adalo will pick a tier for you the next time you rebuild:
Old setting Location Features = on becomes Approximate.
Old setting Location Features = off becomes None.
Your app keeps working. If you need Precise after the migration, change the setting to Precise in Android Settings, then rebuild and resubmit.
The migration only takes effect on rebuild. Your live Play Store build keeps its original permissions until you publish a new AAB.
Common questions
Will switching from Precise to Approximate break my Map component? The map itself still works. The user's "you are here" dot will be less accurate (city-block level instead of meters). If your map's job is just showing nearby items on a map, Approximate is fine.
Does this affect distance-based sort and filter? Distance sort and filter still work on Approximate. The number of miles or kilometers will be slightly less precise, but list ordering and "within X miles" filters are reliable for typical use cases.
Does this change anything on iOS? No. iOS apps use a different permission model and are unaffected by this setting.
My users are reporting "Location not available" on Android after the update. Check that your app's Location Precision is not set to None. If it is set to None, no location feature will work on Android. See Troubleshooting Location Features.
Do I have to change anything? No. If you do nothing, the lazy migration above keeps your app working. The only required action is rebuilding and resubmitting if you want the new permission posture to reach the Play Store. If you genuinely need Precise, you must opt in explicitly.
Related articles
Last updated
Was this helpful?