VANKPA
The decision
Location access should serve a specific feature the user understands. Decide whether the app needs an approximate area, a precise position, or ongoing updates. Collecting more location information than the task requires adds complexity without necessarily improving the experience.
In practice
A service request may only need a manually entered address. A navigation or dispatch feature may require a different level of access. Offer a useful alternative when possible and explain what becomes unavailable if permission is declined.
- Document when location is read, how it is used, where it is stored, and when it expires.
- Test denied permission, changed settings, inaccurate positioning, and battery-sensitive situations.
- Review platform requirements before implementation.
When to take the next step
Request location only after defining the feature that needs it. Review whether a manually supplied address or approximate area would serve the same task.
Questions clients ask
Does every booking app need location permission?
No. An address field or a selected service area may be sufficient.
What if someone declines access?
Explain the affected feature and provide an alternative wherever the workflow supports one.