A journey-reminder app cannot deliver a useful station alert without knowing enough about journey progress and having a way to notify the rider.
What each permission is for
Permissions are not interchangeable. Each one enables a different part of the journey reminder.
- LocationProvides the readings MetroPing uses to estimate station progress.
- Background accessHelps an active journey continue when the screen is locked or another app is open.
- NotificationsLets MetroPing present the destination or interchange reminder when it is needed.
Why the timing of the request matters
Early testers told me that permissions were being requested too soon. They wanted to understand and explore the app before deciding.
That feedback changed how I think about the flow: explain the benefit and limitation in context, then ask when the rider is ready to start the feature that needs it.
You remain in control
A rider should only grant a permission they understand and are comfortable using. Permissions can be reviewed in the phone's settings, though disabling one may limit or stop the related journey feature.
For more detail about information handling, read MetroPing's privacy policy before joining the beta.
Explain first. Ask in context. Request only what the journey needs.
Permission design is part of trust, not a screen to get past as quickly as possible.
Try it on a real Delhi Metro journey.
MetroPing is not affiliated with DMRC. Use it as an additional reminder and share honest feedback about the experience.
Try MetroPing