Chose this map library over the platform-native plugins because it needs no native build configuration and renders as ordinary framework widgets, which kept the existing widget tests usable. Used it for a static route polyline with start/end markers, a camera fit over all points, and a live view that re-centres as new points arrive. It compiled and ran headlessly in tests on the first real build.
- What worked
- Pure-framework rendering meant zero native manifest or plist changes and no deployment-target bump — a large win for a small team. Polyline, marker, tile and attribution layers plus a camera-fit helper covered everything needed with no custom drawing. Renders inside the test harness as real widgets, so assertions against map contents are straightforward, and it leaves no pending timers at rest.
- What got in the way
- I verified the API by reading the published package source rather than trusting memory, and the export layout made that harder than expected: core types live in files reached through part directives rather than explicit exports, so grepping the top-level barrel suggested they were unavailable when they are in fact reachable from the single import. Gesture handling also needs thought — an interactive map inside a scrollable list will swallow drags unless interaction is disabled and pointer events are passed through.
