Why we moved our location stack to HyperTrack

Founded in Nairobi in April 2014, OkHi is on a mission to enable the 4 billion people without a physical address to “be included”. Our solution provides locations with an “OkHi address” comprising of a web link that points to a GPS tag and photo of the house’s gate. A core component of our solution is helping delivery businesses with technology solutions that help them improve their customer experience and internal operations. One of the offerings that we provide is OkDriver that enables drivers and riders to manage their deliveries. Through this app, the driver is able to send an Uber-style tracking link showing their end customers their location in real time.

Screen grabs from OkDriver

I had initially built this delivery platform using the APIs and SDKs provided by Glympse. However as we started scaling up, I encountered many challenges, including:

  • High latency in receiving the locations
  • Inflexibility in the APIs, being unable to develop my features easily with the APIs
  • Reliability of the locations
  • Poor documentation
  • Poor product support
Screen grab of HyperTrack link seen by delivery customer

I started looking out for an alternative, and found: HyperTrack. I was initially skeptical about if I should put in a new SDK into my app. But then I thought of giving it a try. It was just a matter of few hours to put their SDK in my test app and see how it works. I did that over a weekend, and started observing the results. I was amazed by the accuracy of location data that the SDK was able to generate while consuming minimal battery.

The team is truly developer first — always available 24/7 to help me with any integration issues or bugs.

That’s when I decided to continue to pursue building all the location features using HyperTrack. The first and foremost requirement was to have a tracking experience that OkHi’s partners could share with their customers.

HyperTrack API automatically generated a unique short URL for every order that we created. That meant we just needed to take that URL and share it via text message with the delivery customers.

After building our product using HyperTrack’s location stack, we’ve noticed three areas of impact for our partners:

  1. Significantly increased NPS (Net Promoter Score) for our partners
  2. Reduced the call volume between the drivers and the customers by 11%
  3. Riders love our app, “I don’t have to ring the bell or knock on the door because the customer is able to track me live. In addition nowadays I always get a tip.”

Additionally, over these 6 months of usage of HyperTrack, the thing that I loved about the product was the responsiveness of the team. The team is truly developer first — always available 24/7 to help me with any integration issues or bugs.

They are also very responsive to feedbacks and feature requests. For example, we needed to develop a feature to count unique number of views of the tracking URL’s. The HyperTrack team was able to develop that feature within a couple of days and make it available to us (and all the other developers using HyperTrack). I would say it is a no brainer for any developer like me to use the location stack provided by HyperTrack, rather than spend their time & energy on building their own.

Go ahead and check out HyperTrack.

By: Ramogi Ochola (OkHi Engineer), Abhishek Poddar (HyperTrack), & Timbo Drayson (OkHi CEO)