Mapbox

What Mapbox provides

Mapbox is a platform rather than a library. Building a map into an application needs several things, and it supplies most of them.

Map data. The streets, boundaries, water, buildings and place names that make a map a map. Collecting and maintaining that data is an enormous undertaking, and it is the part nobody builds themselves.

Display libraries. Code that draws the map in a browser or a mobile application and handles panning, zooming and interaction.

A styling system. Control over how every feature is drawn.

Location services. Address search, routing and travel time calculations.

Vector maps and why they matter

Older web maps were images. A server produced pictures in advance and the browser assembled them into a grid. Whatever those pictures looked like was what you got.

Mapbox sends vector data instead, and the map is drawn when it is displayed.

The consequences are practical. Styling becomes yours: colours, which features appear, how labels are placed. Zooming behaves properly, with labels adjusting rather than being baked into images at fixed sizes. Maps can be rotated and tilted, because the drawing happens live.

Styling as a design activity

Because every layer is styleable, a Mapbox map can be made to look like part of the product it sits in rather than an obviously borrowed component.

That is a real consideration for consumer applications, where a default map appearance is immediately recognisable and often at odds with the surrounding design. Muted styles for a map that is background context, high contrast for one where the map is the interface.

The trade is that styling is now a task somebody owns. A default style is available and looks fine; a distinctive one takes design work.

The services are half the product

It is easy to think of Mapbox as maps, and for many applications the services matter as much.

Address search turns what a user types into a location the application can use. Routing produces a path between points. Travel time calculations answer how long a journey takes.

Each of these depends on the same underlying map data, and each would be a substantial project to build independently. For a delivery, field service or retail application, they are frequently the reason the platform was chosen.

Who uses it

Mapbox is used by product teams building maps into consumer and business applications, by logistics operations needing routing, and by organisations displaying their own operational data geographically.

Points to consider

It is a commercial service and usage is charged. Pricing is published on the official site and should be reviewed against expected volumes early, since map and service usage in a successful application grows with its audience.

The platform is also broad. Working out which parts you need, and which libraries and services those involve, is worth doing before development starts rather than during it.

For displaying a handful of markers on a simple map, a lighter library may be all that is required.

Getting started

The documentation is organised by product, covering the display libraries, the styling system, uploading custom data and each location service. Displaying a map with a default style and adding a marker is the usual first step, followed by the styling documentation.