Forward thinking companies of all sizes use HyperTrack to build live location features in their products. We make it easy for app developers to build better location-based services, just as Twilio does for communication and Stripe does for payments. Our system clocks over a million hours tracked per month and is growing fast.
“We are like dwarfs sitting on the shoulders of giants. We see more, and things that are more distant, than they did, not because our sight is superior or because we are taller than they, but because they raise us up, and by their great stature add to ours.” – John of Salisbury, Metalogicon, circa 1159
The HyperTrack SDK is active on thousands of devices through 100+ apps across the globe. Users represent all 6 inhabited continents, 2 major smartphone Operating Systems, several tracking use cases and markets, and a variety of network and GPS conditions. We implemented a way for the SDK to record overall battery consumption on the device during the time it was active. This is our first battery benchmarking exercise at a reasonable scale. This goes beyond small scale tests we had done with dozens of users in controlled setups. Turns out, we are able to deliver real-time location tracking with near-zero battery drain.
In this post we share the data that implies that HyperTrack delivers real-time location tracking with near-zero battery drain. We go on to list the battery optimization techniques we used in order to get there.
This is a guest post by Pradyot Ghate, Product Lead, Zomato
We are committed to delivering a simple and hassle-free online food ordering experience to our customers. The customer delight associates at Zomato are the rockstars who make this happen. At peak hours, these associates handle thousands of queries in real-time and a majority of these queries are “where is my order?”.
We invest to empower them with technology to make them efficient. With real-time order tracking powered by HyperTrack, the productivity of these associates has gone up a notch higher. This saves them 1.5 minutes on every query. Continue reading
We had trips on our mind when we first built HyperTrack. We assumed that developers would start tracking a user when they expected the user to be on their way to get some place and stop when they had reached. The assumption failed. Obvious in hindsight, developers expected us to tell them (and not the other way around) when the user was on the way and when they had stopped. All they wanted to do was switch us on or off, and hand over control to HyperTrack to automatically figure out trips and stops in the life of the user. They would keep HyperTrack on through the day, through the week, or just switch it on and leave it on forever. HyperTrack was expected to notify developers about the start and end of these trips and stops, besides other useful events along the way. This led to a re-architecture of our stack that we rolled out with HyperTrack v3 in March. Continue reading
We recently launched the workforce monitoring use case, shared how customers use location events to run their business and helped them get Slack alerts for unexpected events on the field. All of this required a lot of programming and testing.