A visitor opens a marina-services app to find a nearby fuel berth. The app requests precise location immediately, before explaining its purpose, and becomes unusable when the visitor selects approximate access. The product has made its preferred sensor input a prerequisite for a task that could often work with less information.

Mobile location permissions should follow the actual decision the app needs to support. Finding facilities in a harbour district differs from recording an exact arrival point. Define those jobs separately, then ask for the minimum access that lets each one work honestly.

Start with a useful manual path

For a fictional coastal marina directory, allow the visitor to search by harbour or move a map. A manual location is a valid product input, not merely an error state. It also helps someone planning a trip from home rather than standing at the intended destination.

Show which area the results describe. Nearby should not remain an unexplained label after the person enters a different harbour. If the system uses the device location, distinguish that from a selected search area so movement does not unexpectedly replace the user's planning context.

Keep location acquisition separate from ordinary navigation. A person should be able to read facility details, contact information and service descriptions without repeatedly encountering a permission prompt. Making every screen depend on a coordinate turns a narrow feature dependency into a general access barrier.

Ask when the benefit is visible

Android's runtime location guidance recommends requesting access in context and explains approximate access on supported versions. The app should wait for a relevant action, such as choosing use my location, then explain the benefit in language consistent with the platform prompt.

Do not repeatedly interrupt a refusal. Provide the manual path and explain how the person can change access later if they choose. Different operating-system states may require different routes, so test current platform behavior instead of relying on a remembered screenshot.

Foreground discovery does not automatically require background tracking. If another feature truly needs ongoing access, define its separate purpose, user controls and platform requirements. A single nearby search is not a reason to collect a continuous movement history.

Match accuracy to the result you present

Approximate coordinates can support area-level discovery while being unsuitable for claims about a particular entrance or berth. Adjust the result presentation accordingly. Avoid displaying a highly precise distance as though the underlying input identified the visitor's exact position.

Consider stale location as well as accuracy. A reading obtained before the boat moved may be precise for the wrong moment. Keep relevant timing and quality context with the observation, and decide when the interface asks for another reading or falls back to a chosen area.

For the marina directory, an approximate reading could select the general harbour and present a map that the visitor can refine. A feature recording an exact arrival position could explain why more accurate input is needed, while still allowing the visitor to cancel that feature without losing access to the directory.

Store the decision's needs, not every sensor reading

Decide whether coordinates need to leave the device and whether they must be retained at all. A temporary nearby lookup may not require saving a location history to the account. Inspect analytics and third-party integrations as part of the actual data path, because permission granted to the app does not explain every downstream use.

Test approximate access, refusal, a delayed reading, location services disabled and permission changed in system settings. During mobile app development, ask a reviewer to find a facility in every state. The feature succeeds when people understand the area being searched and can complete a useful task without supplying more location precision than the task needs.