The third item above, embed, is the most pertinent to us at Big Boom Design. The first two have to do with using Maps for mobile app development. There was a lot of confusion centered around the pricing of these three items.
These all remain free under 500,000 calls per month. However, you may also notice the top three line-items in the table: Looking at the table above, you see that a heavily trafficked site, especially one containing a map on a frequented page, will run-up charges quickly. The new pricing offers a $200 per month credit to every API key. In some cases, a roughly 1400% increase in fees. Numerous apps and websites had been developed under the assumption that access to these APIs would remain inexpensive. Developers were less than enthused until then, most uses of Google’s APIs fell under a development license that was free for up to 25,000 map views per day. This caused a lot of confusion and consternation. That means that every time a user loads a webpage or an app displaying a Google Map using an API key, Google charges the owner of that API key. Google began charging developers for every call their app or website made to Google’s Maps API server. In the summer of 2018 Google sent shockwaves through the online developer community after announcing that the company would charge for use of its mapping APIs–tools developers use to build programs. One year after Google Maps API pricing changes took effect, how are website developers and owners faring? What difficulties are we facing and what workarounds exist? In this post I’ll breakdown some of the confusion and explain how to install a free Embedded Google Map as well as how to create a new Google Maps API Key.
0 kommentar(er)
