Insane, shocking, outrageous: Developers react to changes in Google Maps API

Is it time to switch to an alternative?

198

This just in: Amazon teams with Esri, HERE to offer location-based data, mapping services

The honeymoon is over, guys – or it will be, on June 11, 2018. Google is making sweeping changes to its Maps API products. And by sweeping, we mean shocking.

Here’s what is happening:

  • The 18 individual APIs Google Maps currently offers are being consolidated into three broad segments – Maps, Routes, and Places. But, you wouldn’t need to make any changes in your existing code; it will work just fine.
  • The Standard (no access to customer support) and Premium plans are being merged into one pay-as-you-go pricing plan. And the new fee structure is not pretty. Google is raising its prices by more than 1,400%. Obviously, no direct comparison figures of old and new prices have been provided by Google, but that’s the average surge that is being reported by developers.
  • All projects will need valid API keys, as Google has insisted before as well. Beginning June 11, keyless access will no longer be supported. Keyless calls to the Maps JavaScript API and Street View API will return low-resolution maps watermarked with “for development purposes only.”
  • You can no longer use the APIs in the first place unless you create a billing account and hand-over your credit card information to Google. This is applicable to all users – even those who have a simple map embedded on their website’s contact page.
  • You will get the first $200 of monthly usage for free. And that should be enough to cover the majority of users who have a simple map embedded on their website as mentioned above. But, for those who use Dynamic Maps, $200 will take care of only 28,000 free page loads per month. Why the emphasis on per month? Because right now, users get 25,000 free page loads per day. Let that sink in.
  • As every dark cloud must have a silver lining, customer support is now going to be free for all.
  • Google is protecting Android app developers from these changes by not charging for Mobile Native Static Maps and Mobile Native Dynamic Maps.

We have always known that the search engine giant had its eyes set on making Maps its next billion dollar business, but when Sundar Pichai shared thoughts on how the company plans to get there, he neglected to mention it would be looking to capitalize on its near monopoly in the market. For a geospatial platform as ubiquitous as Google, these changes are pretty draconian in nature and have the potential of stripping off thousands of location-based small businesses of their key functionality.

Naturally, the reactions from developers on the Internet have not been positive. As this user on Reddit says, “Hmm, yearly 10 000$ -> 200 000$ increase in cost based on our current average usage – twenty times?! Thank you google, investing a fraction of that to migration to competition.” And Twitter exploded with disappointment after the news broke:

For Shyam Sunder, Senior Director at Finland-based automotive startup Link Motion, the mistake of many egos is to be blamed for the monopolistic rise of Google Maps. “Especially in the automotive use case and its developers, the OEMs should see a clear advantage and its significance,” he says. “It’s the customers who are demanding Google Maps and I hope the likes of TomTom, HERE, and Sygic can come up with adoptions like the way Google maps started. Even today I see many issues by such providers who are still finding it tough to get out of their shells.”

So, what do you think geogeeks? Time to switch to an open-source alternative?

Ishveena is a geospatial enthusiast and a veteran of creating and managing compelling digital content for organizations and individuals. When she is not making magic at her desk, you are likely to find her exploring nature, eating her way through life, or binge-watching funny animal videos.

198 COMMENTS

  1. I’m not complaining about it, although I do believe this will discourage users of our new Plugin series we have spent months and lots of dollars developing, called WP Nearby Places, which depends on the Google Maps API – See https://wpnearbyplaces.com. Raising prices is acceptable as long as features and enhancements come along with it, which is not what I’m seeing here yet, but I am hopeful. Thanks for keeping us all up to date Ish.

  2. […] New maps. With this release we move to MapBox for beautiful, fast maps. It runs noticably smoother in the Tesla browser. The hill shading is particularly interesting for us EV owners. (Real-time traffic display is disabled for the time being as it does not work in the fast version of MapBox. Google Maps is no longer an alternative due to their new pricing polity) […]

  3. […] 的API。 导出/导入数据的最常用方法之一是通过应用程序编程接口,更好地称为API。有些商家会让您获取部分数据,或者让您能够将数据写入您的帐户。但这是一个成本。首先,它们的内部数据格式通常是专有的,而不是行业标准。其次,有时API不是核心业务的核心,可以关闭。第三,有时API是其核心业务的核心,价格可以大幅提升。通常,如果您正在阅读或写入托管API,那么您将受到API提供商的支配。我们将此平台称为风险,并且毫不客气地解除平台 启动 […]

Leave a Reply