Making maps work on mobile
summary
Claims that client-side vector rendering replaces raster tiles, cutting data and enabling style changes on the device, with Mapbox tooling and open specs powering the shift. Uses OpenStreetMap data, a Mapbox vector tile pipeline, binary compression via protocol buffers, and webgl to hit ~60fps. Surprising concrete numbers: rendering Bangalore between zoom 13–20 would need about 61,000 tiles if served as rasters, taking ~20–25 minutes to download for offline use. iOS/Android SDKs and Leaflet/mapbox.js integrations demonstrate a working, performant stack.
AI-written summary · about
chapters (5)
- 0:00Start
- 0:15About Map Box
- 2:08How Maps Work in the Browser
- 3:15Two Ways of Interacting with these Maps
- 10:43Rotating the Google Maps App on Your Phone
related talks
16mRaster tiles to vector tiles: how to cross the gulf
17mBoosting Map Performance with Mapbox and Flutter
21mDrawing Maps with OpenGL
49mWhen maps are mission-critical: How Watch Duty powers wildfire safety with Mapbox
40mStronger App Architecture Using Maps- 21mDrawing Maps with OpenGL
01h 34mBuild a Web Map with Open Source Tools
21mMake a map in minutes: How Mapbox is streamlining map development