Always On, for Location service setting for Android and Apple IOS devices, is required by MediRoutes Mobile App, for GPS tracking and used/required for Billing for NEMT Brokers, and other NEMT Business needs.
If a user is logged into the mobile app but subsequently closes their screen or switches to another application, the Android and iOS operating systems only permit continuous location tracking if the app has permission to access location data at all times. This is due to the way these devices manage background applications; they typically disable all functions of apps that are not actively in use. Without the necessary permissions to allow our GPS feature to operate in the background, tracking location is impossible unless the app is open and the phone's screen is active.
Driver will see on the mobile app Message:
"Location Permission Warning, for best Mediroutes experience please enable ALWAYS On Location Permission"
This Message will keep popping up until a Always On permission is set.
Clarifying statements:
1 – We do not have any function outside of the MediRoutes Mobile Application which facilitates communication. This means that if the application is closed, it is not possible for us to send GPS.
2 – We do not have a function outside of the MediRoutes Mobile Application that queries the device for GPS. This means that if the application is closed, it is not possible for us to determine the devices GPS.
3 – The MediRoutes mobile application only sends GPS under the following use cases:
- User must be Logged in to the Mobile App and into their specific route.
- User must be between the Pull Out event and the Pull In event
- We do not send GPS when the user logs in, we only start sending GPS once the user has completed their pull out event.
- We stop sending GPS when the user completes their pull in event.
- There is a way for dispatch to undo the pull-in event to start the GPS sending again, but this cannot occur unless the User is logged in, and even then they would have a schedule change notification indicating that this was done.
- It is not possible for our application to collect or send GPS if the application is not on. If you are unsure if the application is on, it should be clear from the application notification
- The permission requested from the operating system (Android or IOS) would technically allow us to track GPS at any time this application is enabled but our application does not work in this way. We only send GPS after the pull out has completed, and then only until the pull in.
- If you are between the two events, the application is on, but the user has logged out of their route, we will also not be sending GPS. The way our application works requires a user to be logged into a route. Without being logged into a route, our GPS does not work.
We are not the only type of application that requires this. Here are other examples of other Mobile Applications that require the always on GPS permissions:
- Fitness and Activity Tracking Apps (e.g., Strava, Nike Run Club):
- These apps need continuous location access to accurately track your activities, such as running or cycling, in the background, even when you're not actively using the app.
I have one of these installed on my phone, here is the permissions it requires:
Weather Apps with Location-Based Alerts (e.g., The Weather Channel, AccuWeather):
- These apps provide weather forecasts and alerts based on your current location. Constant access to your location ensures that you receive timely updates about weather changes in your area.
I also have a weather app on my phone that requires location services at all times
Other examples of Applications that would require the same permission.
- Geofencing Apps (e.g., Life360, family locator apps):
- These apps use geofencing to monitor when a device enters or leaves a predefined area, requiring continuous location tracking in the background to provide real-time alerts and updates.
- Location-Based Social Networking Apps (e.g., Tinder, Bumble):
- These apps may track your location in the background to update potential matches based on proximity, ensuring that users receive up-to-date information about nearby profiles.
- Fleet Management Apps (e.g., Fleet Complete, Verizon Connect):
- Fleet management apps often require background GPS tracking to monitor the real-time location of vehicles, ensuring efficient management and routing without needing the app to be actively open.
- Field Service Management Apps (e.g., ServiceMax, FieldAware):
- These apps may require background GPS tracking to dispatch technicians, monitor their progress, and optimize service routing, even when the app is not in active use.