Background location needs its own, stronger reason

What it is

Background location is the app still reading coordinates when it is not in the foreground and no one is watching a map: Always Allow, significant-change updates, geofences that fire on a locked screen. It must be requested apart from While Using, and the reason must be stronger than foreground nearby-search—an in-progress navigation, a shared trip, anti-loss. This entry is about location's scope after leaving the foreground. It is not about whether coordinates should be precise or approximate, and not about the one-shot versus ongoing time model that applies to permissions in general.

Why it happens

Foreground location is bounded by "I can see it." Background removes that bound; the coordinate stream can continue after the person thinks they have left. Always Allow is therefore a scope upgrade, not the default continuation of the same grant. Desktop icons do not show whether points are still being taken, so the ask has to happen on its own and say what still happens when the app is not open. Tying background to a foreground Allow trades one visible map use for invisible continuous tracking. The reason has to be stronger because the harm shifts from "located this time" to "a life trail can be stitched."

Studying it

Compare While Using with Always Allow on similar tasks, for both completion and later awareness.

Independent variables: whether the background ask is a separate dialog, whether the reason names off-app behavior, whether a session-scoped background ("only while navigating") is offered. Dependent variables: background grant rate, actual background fixes, judgment of "is it locating after I leave," time until background is revoked.

Lab sessions stay in the foreground and cannot show background invisibility. Multi-day diaries or system access logs are required. Do not treat background grant rate as product success—for most nearby features, a low background grant means foreground was enough.

Where it stops holding

In-progress navigation, live location during a call, vehicle anti-theft still need updates after leaving the foreground; background is the task. Even then, scope should fall back to While Using when the task ends, not leave Always as the default. If a geofence only lights once at a store entrance, request the fence capability rather than a continuous point stream. The web has almost no reliable background location; it should not mimic an Always ask.

Applying it

• Make foreground and background location two requests; success on the first must not auto-fire the second.
• Background copy must include "when you are not using the app" and a stop condition (trip ended, sharing turned off).
• If While Using or a task-scoped background can finish the job, do not request Always.
• Verify by granting While Using, denying Always, and backgrounding for five minutes: no location reports should continue. Then run an in-progress navigation and confirm background points exist only during that task and stop when it ends. Check system location-access history against what the product claimed.

Related

• Within the group: H4.06.1 Precise and approximate location must be requested separately · H4.06.2 Approximate location is enough for most tasks
• Adjacent: H4.07 One-time vs Ongoing Authorization · H4.10 Visibility of Permission State · O2.03 Sensor-Use Indicators
• Search terms: background location · always allow · geofence