Maps can be a challenge in low bandwidth scenarios—they rely on dynamic content being loaded fast and being constantly interactive. We’re tackling this challenge with native mobile SDKs and fast APIs: here are a few ways the full-stack performance of Mapbox is killer.
When you embed a Mapbox-hosted map into your site or app, you refer to it by including the map ID, e.g. justin.gocbkbg3. A tile image URL for this map might look like the following:
Another map ID on my account is justin.pdx_overlay - a neighborhood boundaries layer with partial transparency that I designed in TileMill using open data from Portland’s RLIS portal. Let’s look at the same tile from that map:
But you can also append a PNG bit depth or JPEG quality number:
...13/1303/2930.jpg (original, 19KB)
In many cases, the difference isn’t obvious visually, and in others, the trade-off of speed for detail makes sense. Your app or site could even do bandwidth detection and adjust the map quality on the fly for the best download experience. You can combine the image quality API with the compositing API, since each of these tiles is actually a server-side composition of three separate source tiles.
Built for mobile
Both the compositing and image quality APIs let you customize your maps for speed and low-bandwidth. Whether you use our web services to load images directly or our iOS SDK with full support for the image quality API, Mapbox is mobile-ready and built with the best possible user experience in mind.