We compiled a list of frequently asked technical questions below. If you these do not answer your questions, please send us an email and we will get back to you as soon as possible.
Quickstarts and sample apps are open sourced with the MIT License. We built them to reduce your to build your own app and go to market. We are actively adding more open sourced apps built with HyperTrack that you can fork and re-purpose for your own needs.
Live location tracking is a background process that uses OS location, activity and sensor APIs. We use patented technology to minimize battery drain for high accuracy location tracking. We are constantly improving the energy efficiency of our SDKs. For average movement and phone usage of a mobile worker, HyperTrack should drain single digit % of battery in the day.
In tens of MBs per month for each device.
Yes, you can configure webhooks to stream all movement, activity, and custom markers to your server in real-time.
You can access and query your data up to the beginning of the previous month.
The HyperTrack service runs as a separate component and it is still running when the app that started it is terminated.
Yes. HyperTrack registers a foreground service and user will see a persistent notification as a result. More details in this blog.
Yes, HyperTrack currently provides an Android Views module to subscribe to device and trip notifications programatically. You can use the module to render your own mapping view with the mapping solution of your choice.
Yes. HyperTrack batches up to 12 hours of data while the phone is disconnected from the Internet, and then syncs it up with the server when data connection resumes. Devices with A-GPS may require an active cellular connection for location to be available. These devices might not track as expected while offline.
Start/stop tracking of devices, and start/complete trip, are available only when device is online.