How We reduced our Google Maps API cost
51–60 of 172 posts
Re: How We reduced our Google Maps API cost
#52https://www.eventsofa.de/campus/migrating-away-from-google-m...
Shoutout to Stadia Maps CEO who was always very very helpful.
Re: How We reduced our Google Maps API cost
#53So could increasing pricing under circumstances help to make your customers more creative, more efficient and more ecologically sustainable by making your costumers consume less of your computing power and bandwidth?
Does it matter whether google or the consumer of the google api caches data?
Re: How We reduced our Google Maps API cost
#54Well, that's more clever than a company I did due diligence for. Their strategy was to have a pool of API keys attached to new accounts that would take advantage of the Google Maps API free tier, and monitor its usage. As the free tier usage would run out, the system would roll over to a new API key automatically. Wrote that one up in big red marker in my report...
Is that okay in terms of the ToS? How frequently did someone have to create new accounts? Won't Google just ban the server's IP?
Re: How We reduced our Google Maps API cost
#55Re: How We reduced our Google Maps API cost
#56Like in all of Google's "free" apps, the consumer is the product. They gather your data through Waze and Google maps and sell it for nice money to paying customers. Maybe they can expand on the model a bit and let the paying customers query the API to find out what you were talking while driving. I'm sure that they can find a justification for it. I was trained to think that companies like Google was all about doing…
Re: How We reduced our Google Maps API cost
#57Also given they seem to own the buses, they could give the drivers a rooted Android phone and get the data by reading the memory (or network traffic after reading the TLS key from memory) of their running instance of Google Maps that they are using to drive, which should be undetectable by Google.
Re: How We reduced our Google Maps API cost
#58Like in all of Google's "free" apps, the consumer is the product. They gather your data through Waze and Google maps and sell it for nice money to paying customers. Maybe they can expand on the model a bit and let the paying customers query the API to find out what you were talking while driving. I'm sure that they can find a justification for it. I was trained to think that companies like Google was all about doing…
Sounds like you need some retraining.
Re: How We reduced our Google Maps API cost
#59Like in all of Google's "free" apps, the consumer is the product. They gather your data through Waze and Google maps and sell it for nice money to paying customers. Maybe they can expand on the model a bit and let the paying customers query the API to find out what you were talking while driving. I'm sure that they can find a justification for it. I was trained to think that companies like Google was all about doing…
Re: How We reduced our Google Maps API cost
#60They mention a 94% budget saving but there's no mention of the drop in accuracy (which I'm sure has occurred)?