nickpatrick

Yep, I get it. Working on a self-serve pricing calculator. Reality is that enterprise convos do make sense at sufficient scale. If it does here, our inbox is open!

Out of curiosity, why do you think it's vastly superior?

Appreciate the feedback. We're working on showing the right level of detail at different zoom levels for the different map styles. cc @kocheez75

Should be showing a collapsible ⓘ button on very small screens. We'll take a look and fix.

We are big fans of Felt!

As someone who used to work at an ad tech company, I can tell you that we're very much not an ad tech company. In fact, we set out to build the opposite. More here: https://radar.com/blog/our-commitment-to-privacy

Short, easy-to-spell name that suggests location. It's worked out pretty well for us, and we got the dot com!

Would love to chat. Worth considering best solution given tradeoffs: Cost, coverage, customization options, enterprise-readiness

Our standard policy is that you can cache responses for up to 30 days: https://radar.com/documentation/maps/geocoding#caching

You can charge a lot when you're #1.

Still pretty good in Europe, but more of a gap. International coverage will be a priority in 2024.

Not familiar with this list, but I'm guessing overly aggressive blocking of location APIs. More on our approach here: https://radar.com/trust

Pricing page could def be clearer. Working on it! https://news.ycombinator.com/item?id=37668919

Pricing is per API call right now, but we're planning to add "per session" pricing in future.

Can you share more about what you're hoping to do?

That's a pretty aggressive list...

Google is the gold standard, but our coverage is quite good in the US. We incorporate a mix of open and commercial datasets both for POI and address data.

Old but good post on vector maps vs. raster maps from our friends at CARTO: https://carto.com/blog/raster-vs-vector-whats-the-difference...

Potentially! We're still big fans of Mapbox for highly styled maps. We've just found that Mapbox and Google are overkill for many of our customers.

Stay tuned...!?

A map load is what it sounds like, an API call is a geocoding/search/routing API call. Pricing starts at $0.50 per 1K for both. Pricing page could be clearer, we're working on it!

More details in the post, but Google starts at $7 per 1K map loads and $5 per 1K geocoding API requests, whereas Radar starts at $0.50 per 1K for both. We've roughly been helping our enterprise customers cut their maps bill in half.

Radar CEO here. Welcome any questions or feedback!

If you're looking for a simple, polished, developer-friendly alternative, check out Radar (https://radar.io). Think Twilio/Braze/Amplitude/Segment/Radar vs. SNS/Pinpoint/EventBridge/Location Service.

Great read, David. Thanks for sharing.

One thing that I'd be curious to learn that isn't covered in the write-up: How exactly did you learn all of this? You say "on the job," but can you elaborate? How knowledgeable were you when, say, you raised your first round of financing, and how much did investors help you through the process?

Cool idea. How accurate do you expect the figures to be? Might people whose apps are reviewed particularly slowly be more inclined to report review times, thereby skewing results?

Personally, I think it's intriguing to receive an email immediately after it happens and wonder what went through their mind as they clicked the button.

Just launched my app for this. http://www.defriendalert.com

Inspired by the buzz around Breakup Notifier, last week's "Defriend Day" (http://www.huffingtonpost.com/2011/03/04/defriend-day-etique...), and a good excuse to give Node.js a spin, I just launched a new Facebook app: Defriend Alert. The app sends you an email whenever someone defriends you on Facebook.

http://www.defriendalert.com

I built it over a two day span with Node.js, Express, and MongoDB. It's hosted by Duostack (which is an awesome service, btw). I'm typically a Rails guy, and this was my first Node.js app. Very impressed. Looking forward to cranking out a few more apps over the next few weeks.

Let me know what you think!

"Principal" is a standard career level at Microsoft. There are dozens of principal-level engineers on the Bing team.

To compete with Bing's visual search, perhaps? http://www.bing.com/visualsearch

Also, the domain is a nice bonus. The future of search lies in recommendation and personalization, and Google will eventually want to build a brand to compete with Facebook in that space.