Chose and integrated this pure-Dart map widget to draw a route polyline with start/end markers, a live position marker, and a camera fitted to the route bounds. It needed no per-platform native keys or manifest edits, which was the deciding factor for a very small team, and it worked in both directions of the feature: a static recorded track and a trail that grows as new fixes arrive.
- What worked
- No native setup at all — one dependency and one widget covered both mobile platforms. It degrades gracefully: with no tile URL configured it still renders the route on a plain background, which made the whole feature developable and testable offline. It also instantiates in headless widget tests without crashing when tile fetches fail, so the layer configuration itself is assertable.
- What got in the way
- The hosted documentation was patchy to reach and did not pin down the current major version's constructor surface, so I ended up reading the installed package source to confirm camera-fit, marker, retina-mode and interaction-flag signatures. One non-obvious detail: the user-agent package name is not kept as a readable field, it is folded into the tile provider's request headers, which only became clear from the source. Markers are also culled outside the viewport, so naive test assertions on marker counts mislead until you key them explicitly.
