Posted on 10-16-2013
Fast-forward 7 years, and maps are a central fixture of virtually every web and mobile application we depend on daily. While Google Maps is still the heavyweight in the space, their now classic map interface, proprietary tooling and search centric mindset leaves a huge opportunity for disruption in the app economy, and the venture capital firm Foundry Group is betting that startup mapping provider MapBox is the solution that will de-throne Google, with a 10M investment in MapBox earlier today.
In 2013, when you are looking to deploy a true platform, you have to shed your self-centered approach to technology, do your homework on what are the best practices and standards that exist across your industry, and don't re-invent the wheel or try to keep things closed and proprietary, making everything you do a two-way street that benefits the entire ecosystem. This is how you establish a true platform ecossytem, one that developers will believe in and embrace. This is what MapBox has done by building their platform around four very critical open mapping specifications:
- TileJSON - TileJSON is a standard format for describing various aspects of a map and makes for an easy entry point for loading, showing, and describing maps, allowing developers to keep track of information about maps,where their tiles are stored, their centerpoints, bounds, supported zoom levels, markers data, attribution, and more.
- simplestyle-spec - The simplestyle spec is a practical approach to describing visual markers on a map, for styling markers and maintaining a distinction between content and visual styling can be tricky when annotating maps.
- mbtiles-spec - The mbtiles specification is an open approach to storing tiled map data in SQLite databases for immediate usage and for transfer, making invidual tiles portable and easily migrated between apps and systems.
- utfgrid-spec - UTFGrid is a format for interactive data that uses JSON and can be transferred tile-by-tile to fit maps of any scale, allowing scalable interaction of maps within applications.
Open standards help provide grounding anchors for any platform, and MapBox is going all in, by not just employing these four open specifications--MapBox is also entirely powered by OpenStreetMap, an active community of tens of thousands of dedicated open source mappers who keep MapBox maps up to date and accurate in a real-time, crowdsourced way.
The approach MapBox is taking to building their platform on top of an existing open platform, and embracing the best of breed open standards, sends a signal to its fast evolving ecosystem, that MapBox is not just about building out their own intellectual property like Google, Bing, Apple and other providers are. MapBox is about investing in an open ecosystem of maps, standards, tools and resources that benefit the entire world of mapping.
API Driven Integration
MapBox provides static and REST API access to all aspects of the mapping platform providing developers with programmatic interfaces for all aspects of the mapping ecosystem. Developers can work with maps, tiles, markers and geocoding services directly via API interface, and use SSL to secure integration, and JSONP to integrate with mapping services across any domain.
The ability to customize every layer of a map, making it as meaningful as possible to each application is the future of mapping. MapBox allows for the development of custom maps, markers and related data, allowing developers to define mapping layers as containers of rich context that will benefit the end-user experience and establish millions of virtual map tiles and layers as rich stores of geo and context relevant information.
Next Generation Architecture
MapBox identifies that mobile is a major driver of the growing role maps are playing in our daily lives, with a GPS in all of our pockets, and providing realtime location data to applications. MapBox has invested in providing iOS SDKs for developing rich mapping solutions for the iPhone, including native mapping based upon Apple's MapKit with their MapBox MBXMapkit. Beyond mobile specific SDKs, the MapBox API provides many mobile focused resources including the ability to optimize resolution of mapping images and overall access via modern, mobile friendly web APIs.
Priced to Scale
The pricing of cloud platforms are always an immediate signal of the potential of an ecosystem, and developers have been trained to be weary and avoid deeply integrating with platforms who do not have a clear business model. MapBox has a four tier pricing framework starting at $5 a month, then stepping up to $49, $149 and up to $499 a month. MapBox base pricing is derived from map views and storage with an additional rate for any overage charges. MapBox pricing reflects modern cloud utility pricing that provide developers with an essential pay-as-you-go model, ensuring a healthy approach to monetization that is doable for developers, covers MapBox operating costs while also generating sensible revenue for the company.
Serious Client Portfolio
MapBox isn't just a favorite for the usual alpha tech developer community. The existing portfolio of MapBox users includes tech heavyweights like Foursquare, Evernote, Github and Uber including leading news and media groups like NPR, US Today, Financial Times and National Geographic. This is just a sampling of some of the best known brands who have embraced MapBox, and understand the importance of custom, open attractive maps that compliment their brand, while also providing the best user experience possible.
A Platform Blueprint
MapBox is a model of how successful technology ecosystems will deliver the resources developers will need to build the next generation of web and mobile applications.
comments powered by Disqus
Winning in the API Economy
|Download as PDF|
Latest Blog Posts
- Adding The OpenEd API To The API Commons
- PR People For APIs
- I Will Be At API Days in Paris This Week, Will You Be There?
- Government Services Schemas With JSON-LD
- University of California Student Senate Submits Bill Stating Student Information Systems Must Have API
- Generating The Utility APIs I Need For Each Developer Portal
- An API For Your Github GeoJSON Stores
- Server Side API Templates On AWS Cloud Formation And OpenShift
- Hypermedia In The Wild: Amazon AppStream API
- API Search Endpoint Using Solr