Subscribe
Sign in
Radar — Location data infrastructure
Radar is location data infrastructure. You can use Radar SDKs and APIs to add location context to your apps with just a few lines of code.
58
Replies
@imcatnoone Thanks, Cat! We love what you're building and we're excited to be working with you!
Hunter
I am very excited to introduce you to Radar, a location platform for mobile apps. Helping launch Radar today is especially fun because they are a part of the first Expa Labs program, are my former colleagues from Foursquare, and have built an amazing product.
Radar helps companies collect, analyze, and act on location data. It seems obvious to teams now to add an analytics platform to their mobile apps, and the same will become true for location platforms. Radar can help teams build better products and services with location, thereby increasing engagement, increasing revenue, or improving operations.
I hope you’ll check it out!
Thanks, @ericfriedman!
Hey, Product Hunt! I'm Nick, one of the co-founders.
We're building Radar because, ten years into the smartphone era, it's still way too hard to build products and services with location. We wrote more about this problem and how we're solving it here: https://blog.onradar.com/introdu...
We'd love to hear your feedback and answer your questions!
@ericfriedman This looks really cool! Are there any plans on supporting Progressive Web Apps?
@thehashrocket Thanks! @kunalslab asked the same question below, so I'll share the same response: We're focused on native mobile apps for now, since that's where we see the biggest pain and the biggest opportunity to start. But Radar could in theory ingest and make sense of any locations sent to our API, whether from our native mobile SDKs or from a web JavaScript library, from historical data, or from other types of devices.
@taykcrane Great question. We’re seeing three main use cases emerge for using Radar: increasing revenue, increasing engagement and improving operations. For instance, using Radar to notify people when they are in a certain place so that they can make a purchase (increasing revenue), using Radar to personalize an in app experience to immediately show content about a place a user is in (increasing engagement), using Radar for delivery tracking/workforce management (improving operations). Specifically, the verticals we think will benefit the most from creating great location products are retail, food/QSR, delivery, workforce management, social and travel. Hope that helps!
@cobyberman and what are the challenges of doing this now? It sounds like there are many but just want to better understand.
Foe example, use case #2 that you mentioned, this seems pretty commonplace for apps that use the phone's location sharing feature.
@taykcrane check out @nickpatricks post describing the problem of building this from scratch: https://blog.onradar.com/introdu...
Congrats to Coby and Nick. As others have mentioned, this is an incredible team that's been assembled to pull this off. Excited to see the company grow.
The location platform the Radar team has built is what true product owners and engineers have been waiting for. Couldn't think of a group better suited to pull this off.
Whether you're a national retailer or a local bar it always makes more sense to geofence than install physical beacons to drive context and additional commerce, and now it's possible for any use case. Plus the team is amongst the best I've met. Excited :)
Are you required to set geofences for notifications or can you notify me when a user enters a new city or leaves their home geo?
@nalin Great question. Right now you're required to set up geofences, but we'll be adding out-of-the-box support for these types of insights and events in the future. We have a few customers who've set up city and/or airport geofences with appropriate metadata exactly for this purpose. They've set up webhooks that listen for entry/exit events, update user profiles, and send push notifications as appropriate when users move between cities.
Awesome! Are you seeing similar issues for web apps on mobile that require location/geofencing? If so, any plans to support more than native apps?
@kunalslab Great question! We're focused on native mobile apps for now, since that's where we see the biggest pain and the biggest opportunity to start. But Radar could in theory ingest and make sense of any locations sent to our API, whether from our native mobile SDKs or from a web JavaScript library, from historical data, or from other types of devices.
@nickpatrick @kunalslab I think this would be super interesting though I get that companies like Algolia kinda have that built in too.
@nickpatrick thanks, I'll take a look at the APIs.
@stevenlu yes, though Algolia is tuned toward search. I like that Radar is focused on location only.
We've been testing radar for a few months @winendine now. The product is awesome and saves us a ton of time - we love what these guys are doing. Congrats @cobyberman and @nickpatrick!
I'm v excited by Radar and what it means for location services. I sometimes feel like we're still pre-search internet for the physical world ... and it still needs to be indexed. Radar is a step in the right direction.
well done @nickpatrick and @cobyberman. very excited to wake up to a PH launch today :)
Hey cool stuff! Building location features is definitely more painful than it needs to be. Congrats on launching this. have you seen HyperTrack.com? how are you guys different?
Stark