dennisgorelik: 2020-06-13 in my home office (Default)
Today "Google Maps Platform <google-maps-platform-noreply@google.com>
emailed me (and other users) how they "simplified product structure", which means that they increase prices 10x+.

So, instead of $10/month - $50/month we pay now -- we will have to pay somewhere between $200/month and $3000/month (depending on how much we downsize our Google Maps API usage).

Google Geocoding API prices change from "$0.50 per 1000 requests" to "$5 per 1000 requests".

The pricing time bomb is scheduled to explode on 2018 June 11.


On our to-do list:
1) Eliminate Google Maps from postjobfree.com pages (/job and /resume pages).
2) Find a replacement for Google Geocoding API.

The most promising Geocoding API alternatives so far:
1) https://geocod.io/pricing/
2) https://geocoder.opencagedata.com/pricing

Other alternatives

Discussion on Hacker News

Google Maps API team wants to get paid more (2016)

Today we are announcing important changes, including our new name - Google Maps Platform, a simplified product structure, pay as you go pricing for all, and more. Please take a few minutes to review the announcement to familiarize yourself with the upcoming changes.

We would like to highlight a few updates that may impact your implementation. Beginning June 11th, we are launching our new pricing plan and providing all users access to support. We’ll continue to offer a free tier — all developers will receive $200 of free monthly usage of our core products.

How does this affect your current account(s)?

Billing Account: 00B0C3-2BDF32-******

Based on your usage over the last 3 months and our new pricing plan, you may be eligible for a volume discount. Please fill out this form to provide additional information about your account, and a Google representative will contact you within the next two weeks.

We want to help you with the transition to the new pricing plan. To do that, we're offering 2 months of credits which we will apply automatically to your billing account.

We want to support you along the way. Please read our Guide for Existing Users to understand how these changes may impact your account and what steps you need to take.

Thank you for using Google Maps Platform.
dennisgorelik: (2009)
Google Maps was an excellent product when it was released back in 2004:
1) It was convenient (allowed map drag&drop and zoom in/out with mouse).
2) It was fast.

But then founders left, incompetent middle managers took over, and decline of Google Maps team began:
1) Now Google Maps is much slower than it was.
To understand how much slower - you should try using old version of Google Maps that is still available at https://www.google.com/moon/
Current Google Maps is about 5 times slower on zooming in/out that Google Moon (old Google Maps framework).
2) Google Maps is not even able to show cursor on their location "Search Google Maps" input textbox:
https://www.google.com/maps
Immediately after load cursor blinks once and then disappears (in Google Chrome. In Internet Explorer cursor stays visible).
Even Microsoft Maps team is able to keep cursor visible in their address input Inbox: https://www.bing.com/mapspreview

Anyway, that was just a preface, here is my today story.
That story is about my interaction with Google Maps API team.

Google Maps API sales squeeze
Couple of days ago Google Maps API team introduced changes in their pricing:
---
http://googlegeodevelopers.blogspot.com/2016/06/building-for-scale-updates-to-google.html
1. We no longer support keyless access (any request that doesn't include an API key).
...
3. We have reduced the daily map load maximum limit you can purchase for Google Maps JavaScript API... from 1,000,000 to 100,000 requests per API.
4. We now count Google Maps JavaScript API client-side requests towards the daily limit of the associated web service API.
---

It is actually hard to understand what they mean. Here is the gist of it:
1) Google Maps usage by users from browsers that was free in the past - is not free anymore.
2) Reasonable standard plan prices were available earlier for up to 1M requests per day.
Now that limit is 10x lower at 0.1M requests per day.

You might think it is not a big deal to go up and switch from Standard Plan to Premium Plan when you scale your business.
I thought that too. Until I finally managed to find out how much Premium Plan costs.
Premium Plan costs 40 times more than Standard Plan.
40 times, Karl!

Standard plan is $0.50 per 1000 requests.
Premium plan is $20 per 1000 requests.
(That is approximation. Actual prices are a little bit lower due to free quotas every plan has).

But wait, there is more.
Premium plans starts at $10000/year minimum.

And more:
-----
https://developers.google.com/maps/pricing-and-plans/
Premium Plan: If you charge a subscription fee beyond the Play or App stores, you require the Premium Plan. Web service APIs and the JavaScript API require the Premium Plan.
-----
If you believe that statement, then pretty much everyone who uses Google Maps Web service API (e.g. geocoding) or JavaScript API (typical Google Maps snippet on the web site) must subscribe to Premium Plan and shell out $10K/year.

On the other hand, it contradicts with the whole idea for the Standard Plan pricing.
Who does qualify for Standard Plan pricing, if everyone must use Premium Plan anyway?

I wanted to clarify that Premium Plan issue and spoke with Gregory from Google Maps team. He told me that we must pay, because we have premium subscriptions for our product.
It did not matter that we are well below 100,000 requests per day (we average about 2,000 geocoding requests per day and about 25,000 map requests per day).
It did not matter that 99% of our usage is free for our users.
According to Gregory, because premium users use our product (job postings) and our product uses Google Maps Geocoding, we must use Premium Plan.
Gregory did NOT give me any examples of businesses that qualify for Standard plan pricing.

Analysis
I think Google Maps API team managers intentionally crafted such a vague "Standard Plan vs Premium Plan" message.
It allows them to sit on two chairs at the same time:
1) Squeeze businesses for more money.
2) Soften public outrage from that squeeze and encourage startups to start using Google Maps API.

I think that this strategy is wrong and indicates incompetence of Google Maps API management team.
Confusing and squeezing customers like that is not a sound business practice.

My guess is what Google Maps API management is trying to do now with most businesses - is the same strategy they used for years with largest web businesses. That explains why big web sites rarely use Google Maps and use Bing Maps instead (e.g. Zillow). Microsoft treats their business customers much better than Google Maps team does.

What is next?
Here's my business plan so far:
1) Remove Google Maps from postjobfree.com
It is not clear if having maps is beneficial to our users (job seekers and recruiters).
2) Consider switching to another geocoding provider.
E.g.:
- OpenCageData - $100/month for up to 20,000 requests per day.
- developer.here.com - $59/month for 150,000 geocoding requests per month.

What do you think I should do?
1) Do you have a recommendation for good geocoding service?
2) Are maps valuable on job and resume pages?

Update 1:
Select transcript from conversation with Gregory
===================
[0:55:22]
Gregory: We still have cost on our side. We have to run a business. There is whole a lot of overhead in that map... Especially in terms of keeping it up to date, keeping it accurate, keeping it at scale. So, 10 thousand dollars is the minimum we came up with.
And you can argue it is not appropriate and fair. And I tell you very honestly - you won't be alone. But at the end of the day it is still $10K.
.....
[1:07:10]
Gregory: The big reason that we switches at the beginning of the year [2016] and started offering Standard and Premium plan was to cast a wider net. And to get more people like yourself that are longer tail into using our maps. But again, this is where I know you may find a difference, but there are some cases where you just can't fall into the Standard. But there are a lot of people who are able to use the Standard now and, you know, pay as they go, and grow and everything. But certain use cases just didn't qualify. And I think that's the part that you've just haven't been able to accept. Because of either you are saying your are small and not profitable [DG: I did not say that I'm not profitable] I totally clear you loud and clear on that. Or you are not offering something that's paid.

And I think you are trying to use it on both sides, when you are saying it's free and paid. And I explained to you when it's both we've been given a directive that the paid trumps the free.
[1:08:20]

[1:09:20]
Gregory: I think at this point we just need to follow the truth. So, how do you wanna leave it. What actions do you need on our side.

Dennis: I guess nothing. Let's keep going as we were going. Google already charges me. You lowered the quotas. So now I'm more likely to hit this. You started to charge for something that was free before. And I am fine with this.
But I am not fine with you increasing it straight to $10,000 right now.

Gregory: No. I'm not gonna do that. If you won't signing the contract - it won't happen. But I can't control what our Compliance team is doing and how they are checking. And if they check and call then it is something that has to be dealt with between you and the Compliance team.

Dennis: My understanding is that the Compliance team probably would be interested in insisting on Premium License when we are closer to 100,000 requests per day. May be not reach it, but close.

Gregory: [laughing in ironic "Steve Balmer" style] I love how you are taking this assumption.

Dennis: And you know why I'm taking this assumption? Because Google actually lowered that quota from 1 million to 100,000 requests per day.

Gregory: You are referring to the blog post? Is that what you are referring to?

Dennis: Blog post and emails that I received. The change that happened few days ago. The limit was 1 million...

Gregory: Do you have the copy of the letter you received?

Dennis: Yes I have.

Gregory: Do you mind just sending it to us? So I could share.
Because this is actually good feedback, Dennis.
Because I could say "this letter has customer thinking. This is how this should be interpreted".
And again, we need to recognize if that's, you know, unclear or ambiguous, so we don't have people like you, you know, worried about or confused. We should try to make it clear. You should send it to me at gregory at google dot com.

Gregory: I think the best thing to do... I really think it would be wise to bounce it off someone on your team, ideally a legal person.
And again if you feel like your use case needs more scrutiny on our side, if you can just put that in writing - what your use case is -- I'm happy to share it with our team members.

Dennis: One more thing about Premium. Say, some time in the future I finally switch to Premium.
$10,000 is the minimum fee. But how is it defined? There is no upper boundary, right?
Like what is the charge?

Gregory: [Laughing] "There is no upper boundary", oh boy. Jeremy, what do you think: "OEM"? Or something else?

Jeremy: Yeah.

Gregory: So you'd get 500,000 map credits per year. And the map credit is defined as the load of the map. The visual load of the map is the map credit. So you'd get half million of those.
You'd get free 100,000 geocodes per day. You go over that - then it would start to decrement your map credit.

Dennis: Ok. Free - 1,000

Gregory: No-no. I did not say 1,000. I said 100,000. Geocodes.

Dennis: Ok. 100,000 geocodes. With Standard it's like 2,500.

Gregory: Right.
.....

[1:14:17]
Dennis: And if it is above 500,000 then what is the price?

Gregory: We have different tiers. If you are just barely over, you can just get another quantity of 500,000.
If it looks like you are about double that rate, you just sign up for quantity 2, so you get a million at $20K.
But as far as price break - I think 5 million.
===================

Update 2:
According to this explanation, postjobfree.com does NOT fall under any of cases below that require Premium Plan:
-------------
https://developers.google.com/maps/faq#understanding-terms-of-service
Can I use the Google Maps API on a commercial website?
As long as your site is generally accessible to consumers without charge, you may use the Google Maps API. For example, if your website is supported by advertising, it likely falls within the Google Maps API Terms of Service. If you charge people to place information on your map (e.g. to list their homes for sale), but you display this information using the Google Maps API on a free part of your site, you'll also meet the Google Maps API Terms of Service.

However, not all commercial uses are allowed. For example, if your site meets any of the following criteria you must purchase the appropriate Google Maps APIs Premium Plan license:
- Your site is only available to paying customers.
- Your site is only accessible within your company or on your intranet.
- Your application relates to enterprise dispatch, fleet management, business asset tracking, or similar applications.
Remember, Google reserves the right to suspend or terminate your use of the Google Maps API at any time, so please ensure that you read the Terms of Service carefully.
-------------
So Gregory's claim that PostJobFree must use Google Maps API Premium Plan contradicts to that explanation.
I guess Gregory is hard pressed by his bosses to push more Google Maps API users to Premium Plan.
And his bosses probably got a "get profitable or die" message from their superiors.

Links:
Quora: Google Maps API vs Bing Maps API: which is more cost efficient to use?
StackOverflow: Google Maps geocoding vs Bing Maps geocoding
dennisgorelik: (2009)
Google Maps API team just sent me couple of emails.
The gist of the changes is that:
1) Going forward Google Maps API strongly encourages using API key, even from JavaScript version that runs from users' browsers.
2) "Google Maps JavaScript API" and "Google Maps Geocoding API" are going to use free quota associated with that API key.
That means Google is likely to start charging for these requests much sooner.

The prices are not high: $0.50 per 1000 requests.
That means for 1 cent we can make 20 requests.

It is a good deal for Geocoding API that we really need.
It is not such a good deal for rendering Google Maps snippets on our web site, because we do not really need them that much.

So far I plan to ignore their advise "to begin using a key for all requests immediately.", and rely on their claim that "For the time being your domain has been whitelisted for keyless usage."
I guess using keyless requests from browser should be ok. (PostJobFree already uses API key for server-side requests to Google Maps Geocoding API).

I am also tempted to remove Google Maps from jobs and resume pages on postjobfree.com
It is not obvious if having these Google Maps snippet our PostJobFree pages adds value to our users.

What do you think I should do?
From: Google Maps APIs 
To: catchall@r.postjobfree.com
Date: Wednesday, June 22, 2016, 8:43:08 PM
Subject: [Action required] Google Maps API requests are missing a project key

===8<==============Original message text===============
This email is intended for the administrator of postjobfree.com. If you are not affiliated with postjobfree.com, please disregard.

Hello developer,

Today we announced updates for the Google Maps API Standard Plan, including marking keyless usage of any of the Google Maps APIs as unsupported. As part of these changes, we are attempting to contact developers making requests without a key to advise them of possible impacts to their implementation.

We notice that postjobfree.com is accessing Google Maps APIs without a key and believe you may administer that domain. For the time being your domain has been whitelisted for keyless usage. However, API keys allow Google to protect an application's uptime and contact developers with mandatory service announcements, therefore we advise you to begin using a key for all requests immediately. 

To register a free API key for your application:
Visit the Google API Manager Console.
Create or select a project and click "Continue" to enable APIs and related services.
On the Credentials page, get a Browser Key (and set the API credentials).
Add your API key to all application requests.
To prevent quota theft, secure your API key following these best practices.
(Optional) Enable billing. See Usage Limits for more information.
Note if you have an existing Browser key, you may use that key.
For more information on these changes, please refer to the Standard Plan updates summary.

Thanks for using our APIs, 
The Google Maps API team 
© 2016 Google Inc., 1600 Amphitheatre Parkway, Mountain View, CA 94043 
You've received this mandatory email service announcement about important changes to your Google Maps for Work product or account. 
===8<===========End of original message text===========


Update: Decline of Google Maps team

Profile

dennisgorelik: 2020-06-13 in my home office (Default)
Dennis Gorelik

June 2025

S M T W T F S
1234 567
891011 12 13 14
15161718192021
22232425262728
2930     

Syndicate

RSS Atom

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags
Page generated Jun. 18th, 2025 04:40 pm
Powered by Dreamwidth Studios