A customer who knows the branch name can search for it without sharing the position of their phone. Offer a visible list or area search first. When someone chooses a nearby search, explain how the result will help them and request the access that feature needs. Android's developer guidance says to ask in the context of the feature when the user interacts with it.
Start with two different customer journeys
Picture a customer sitting at home who wants to book near work tomorrow. Even a perfectly accurate location reading points to the wrong starting place. Let that person choose an area or enter a branch name and inspect opening information before continuing. Another customer is already out and wants to find a nearby counter. A clearly labelled action to use the current location fits that second journey. Sketch both routes to the same branch details screen before discussing the wording of a permission prompt.
Decide what accuracy changes in the result
Android supports a distinction between approximate and precise location on supported versions. Work through a case where two branches serve adjacent districts. If the position is approximate, display the candidate branches with their areas and addresses and let the customer choose. If the list is sorted by estimated distance, make that basis clear. Do not silently select a collection point for an order just because it appeared at the top of the list. Ask the designer to show what the customer sees when two branches have similar names.
Keep a declined request usable
On paper, cross out the location reading and walk through the nearby search again. What remains on screen? Give the customer a route back to the list and keep any area or search term already entered. A short explanation beside the manual search is more useful than repeatedly opening a prompt. For a branch finder that only needs a position during a search, ask the team what customer action would justify requesting access while the app is closed. Omit that request if the team cannot identify a separate need.
Approve behaviour on a real device
Start with a fresh permission state. Try manual search, allow approximate access, decline the request and return after changing the setting. Record the branch selected and the address shown at checkout or booking in each scenario. Run a final test with a customer choosing a branch near their workplace while standing elsewhere. If the selection survives a trip back to the list, the app supports an intentional choice as well as a convenient nearby suggestion.
Sources and further reading
Prepared with AI assistance and checked against the sources listed above. Planning examples are illustrative; your project scope is agreed separately.
