Posted on 01-23-2014
According to Keir Clark over at Google Maps Mania, we are seeing The Slow Death of the Google Maps API. Who else could read the tea leaves, when it comes to an API, than a blogger who is dedicated to covering the innovation that comes out of a single API ecosystem.
Clark has noticed that "there seems little sign of the Google Maps API team returning from their two year vacation”, and "at the same time the MapBox team has continued to innovate and has now become the maps API of choice for most developers”.
While nobody knows the reasons Google Maps has stopped innovating (except Google), it is clear that you can’t stop delivering value to developers, or they will migrate elsewhere to find the API resources they need for their applications—it doesn’t matter if you are Google, or any other tech giant.
The Google Maps API is one of the API pioneers listed on my History of APIs, but much like Delicious, maybe the age of Google Maps is coming to a close. I’m sure many mainstream websites and applications will use Google by default because of the advertising and SEO opportunities, but for developers who care about providing beautiful, seamlessly blended maps that add value to their websites and apps, I think Google Maps just isn’t going to do it anymore.
comments powered by Disqus
Winning in the API Economy
|Download as PDF|
Latest Blog Posts
- What Version Of The API Economy Are You Investing In?
- I Am Up To 34 APIs Out Of The Netherlands
- Hello World Product API With Blueprint, RAML And Swagger
- The New Github Developer Program and Integrations Page
- I Have A Valuable API Resource, What Now?
- A Better Understanding Of Government APIs And Their Consumers Before Considering Charging For Use
- So You Wanna Do a Spreadsheet or Database To API Startup
- Jumpstarting the Automobile API Conversation With Carvoyant
- Some Of The Common Building Blocks of Payment APIs
- API Badging and Credentialing To Demonstrate Skills