Boosting Map Performance with Mapbox and Flutter
summary
App moves from imperative Mapbox annotations and full Firebase downloads to serving tiled GeoJSON sources via a CMS and Map Toolkit, using the official Mapbox SDK and layer-based rendering. Interaction uses queryRenderedFeatures for taps and data-driven styling with expressions and layer-based styling so color, name and selection come from feature properties. Result scales from about 10 trails with 300–21,000 accommodations each, cuts initial load from ~30 seconds to effectively instant, and eliminates per-feature UI plumbing.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:10Problem overview
- 3:58Firebase and Mapbox challenges
- 7:30Vector sources and styling
- 9:59Declarative styling shift
- 11:24Handling map interactions
- 13:09Data-driven styling
- 15:17Results and improvements
- 16:01Key lessons
- 16:42Q&A
related talks
21mMake a map in minutes: How Mapbox is streamlining map development
15mMaking maps work on mobile
40mStronger App Architecture Using Maps
36mBuilding the NYC Public Space App with Flutter and Mapbox
49mWhen maps are mission-critical: How Watch Duty powers wildfire safety with Mapbox
51mWays to get data into Mapbox maps
52mUplevel your map icons
49mGetting started with the Maps SDK for Flutter