Lorixen.
EN

Location permissions in driver and field-staff apps

Short answer: Most driver and field-staff apps do not need true "background" location. They need location while a shift or delivery is active, which Android treats as foreground access when it runs in a foreground service with a visible notification, and which iOS can deliver under "While Using the App" with background location updates enabled. Ask for the smallest level that makes the core feature work, ask at the moment the driver starts a job, and design a clear fallback for drivers who say no. "Always" access brings extra Play Console paperwork and closer review, so treat it as the exception.

If you are briefing a developer on a delivery, courier or technician app, settle these questions in the specification before anyone writes code.

What each operating system actually asks

Both platforms separate when the app may read location from how precisely.

iOS (Core Location) Android
Basic level When in Use: location while the app is in use Foreground: while an activity is visible or a foreground service runs
Elevated level Always: updates at any time, and the system can relaunch the app for some location events Background: requires the ACCESS_BACKGROUND_LOCATION permission on Android 10 and higher
Precision Full or reduced accuracy; apps can request temporary full accuracy with a purpose string Approximate (about 3 km² area) or precise (usually within about 50 m), per Android's docs
What the person sees System alert with your usage description; options include Allow Once and While Using the App Runtime permission dialog; a reminder notification later if background access is used
Text you must supply NSLocationWhenInUseUsageDescription, plus NSLocationAlwaysAndWhenInUseUsageDescription for Always No purpose string in the dialog, but Play requires an in-app disclosure for background use

Details from Apple's Core Location documentation and Android's location permission guides, as of November 2026.

iOS in practice

Apple describes When in Use as the preferred choice because it is better for privacy and battery life. On iOS, an app with When in Use authorization and background location updates enabled keeps running in the background while location services are active. That covers a driver who locks the phone mid-route. What When in Use does not do is relaunch a terminated app; Always authorization can, for significant location changes, visits and region monitoring.

Two practical points from Apple's documentation: if the usage description keys are missing, authorization requests fail immediately, and if your app already has When in Use you can request Always later, but only once. So the second ask has to land at the right moment.

Android in practice

Android counts an app as using foreground location when one of its activities is visible or it runs a foreground service, which shows a persistent notification and keeps access when the driver presses Home or turns the screen off. On Android 10 and higher, that service must declare the "location" foreground service type. Anything outside those situations is background location and needs ACCESS_BACKGROUND_LOCATION.

Android also warns that the user may grant approximate location only, and your app should still work if they do. If a feature truly needs precise location, you can ask for an upgrade.

What store review looks at

Google Play. Play's location policy page (as of November 2026) says background location is restricted to apps where it is core functionality with a significant benefit to users, and that apps using it must be approved through the permissions declaration in Play Console, or updates may be blocked. The submission needs a declaration form describing one location feature, a short video showing that feature and your prominent in-app disclosure, and a privacy policy in the app and on the store listing. Play also lists delivery tracking "for users (not drivers)" as an example of a feature that could use foreground access instead.

Foreground services are reviewed too. Play's page says the service must start as a continuation of a user-initiated action and stop as soon as that task is done. A "Start shift" or "Start delivery" button followed by a "Finish" step fits this pattern naturally.

Apple. The App Review Guidelines say to use location only when it is directly relevant to the app's features, to notify and obtain consent, and to explain the purpose in the app. Guideline 2.5.4 allows background services only for their intended purposes, and location is one of them. The guidelines also say apps should not rapidly drain battery.

Designing the ask

The permission dialog appears once; a badly timed ask is hard to recover from. Apple's guidance is to request authorization when someone engages a part of the app that needs location, not at launch. For a driver app, a sensible sequence is:

  1. Sign-in and onboarding without any location prompt. Show the job list first.
  2. A short explainer screen when the driver taps "Start shift". One line on what is tracked (position during active jobs), when it stops (when the shift ends) and who sees it (dispatch and the customer's tracking link).
  3. The system prompt for When in Use / foreground location.
  4. Only if a feature genuinely needs it, a later request for Always or background location, tied to that feature, such as automatic arrival detection at a geofenced depot.

Battery and accuracy choices

Write these into the brief rather than leaving them to defaults:

  • Update frequency while moving vs stopped. Frequent updates on the road, sparse updates at a customer's door.
  • Precision per feature. Proof of arrival may need precise location; showing "driver is in your area" does not.
  • Android's background limits. Android notes that apps running in the background on Android 8.0 and higher receive location updates only a few times each hour, another reason to use a foreground service during active jobs.
  • Third-party SDKs. Android's guide reminds developers that location access by an SDK or library is attributed to your app. Ask your developer to list every SDK that touches location.

Fallbacks when the driver says no

Plan these screens up front:

  • Denied entirely: let the driver work with manual status buttons ("Arrived", "Delivered") and an address-based ETA instead of live tracking. Show a gentle banner explaining what stops working and a button that opens system settings.
  • Approximate only: keep job lists and navigation hand-off working; request precise location only for the step that needs it (for example, proof of delivery).
  • Allow Once on iOS: expect the prompt again next session, and make starting a shift the natural moment for it.
  • Permission revoked mid-shift: iOS reports authorization changes to the app's location manager; on both platforms, check the permission at each shift start and pause tracking (and tell dispatch) rather than failing silently.

Data handling for staff location (how long you keep routes, who can see them) is a policy question for your business; set it with your advisers and check the rules where you operate.

FAQ

Does a delivery driver app need "Always" location?

Usually not. Tracking during an active delivery fits foreground access on Android (via a foreground service) and When in Use with background updates on iOS. Always or background access is for features that must work when the driver hasn't started anything in the app, such as geofence alerts.

Why was our Play submission flagged for background location?

Common reasons are a manifest that includes ACCESS_BACKGROUND_LOCATION without a declared core feature, a missing video or in-app disclosure, or an SDK requesting the permission. Remove it if the feature can run in the foreground.

Can we track drivers after their shift ends?

Design the app so tracking stops at "End shift". Play expects a foreground service to stop when the user-initiated task is complete, and continuous after-hours tracking raises review and trust problems on both stores.

Location rules shape the whole driver experience, so they belong in the first draft of your app brief, and we can help you write that brief.

Sources

WhatsAppLet’s talk