fbpx

EveryDeveloper

Technical Content Strategy for Dev-focused Companies

Oldest Web Map Provider to Slowly Close its API

By

Long before there was Google Maps, let alone the Google Maps API, one provider stood tall and proud, synonymous with maps on the web: MapQuest. Now MapQuest will discontinue its JavaScript API that competes with Google and other map APIs. Though the API will go away, MapQuest will remain in the dev-focused map arena through mobile SDKs and open tools.

The map old timer was a Web 1.0 unicorn, acquired by AOL for over a billion dollars. Before the modern API even existed, MapQuest provided software solutions to embed maps on other sites. Yet, when Google Maps enabled slick, JavaScript-based maps, the company struggled to keep up. Though it differentiated itself through support of community projects like OpenStreetMap, the Google momentum made it difficult to earn developer mindshare.

With a renewed focus on mobile SDKs and its latest Leaflet plugin, MapQuest decided to kill its API and other older tools:

Today, the performance, consistency and capabilities of our Leaflet Plugins has progressed, making them an increasingly better alternative to our legacy Flash and JavaScript mapping SDKs. As a result, we’re beginning the deprecation of these services. Below are the retirement dates for these mapping SDKs:

  • Flash Maps SDK (Licensed, Open, Mobile): 6/6/2017
  • JavaScript Maps API (Licensed & Open): 6/5/2018
  • Leaflet 1.1, 1.2, 1.3: 6/6/2017
  • iOS and Android mobile SDKs v1: 9/6/2016

As noted, the JavaScript Maps API will not completely go away for two years. Likely, this is because MapQuest has a non-trivial number of paying customers (and free users) integrated. Maps that are fully integrated into a website experience can take a great effort to migrate. Two years is a healthy amount of time, but no developer ever wants to have to make that kind of move.

MapQuest’s modern approach is to suggest their plugin to the popular open source Leaflet library. Super-customization map startup MapBox suggests Leaflet exclusively. In each case, Leaflet holds the standard map controls, using tiles from each provider. Google Maps terms of service do not allow developers to use its tiles outside of the Google Maps API, but there is a Leaflet plugin built as a wrapper for Google Maps.

Any changes in Map APIs will continue to be viewed through the lens of a Google-dominant market. It is by far the 800 pound gorilla of mapping. It no longer made sense for MapQuest to go head to head with its own JavaScript API, but I’m certainly happy that it remains within a market it helped create.