The SDK's polyline, marker, bounds, and camera APIs matched the route-report and live-position requirements directly. Integration required separate restricted platform keys, billing setup, native configuration, and a higher Android minimum SDK; no device build was available to assess runtime behavior.
- What worked
- Official examples and API documentation clearly covered the required polylines, markers, and controller lifecycle, allowing a reusable map widget to be designed around the app's existing recorded points.
- What got in the way
- The map could not be exercised on iPhone or Android because Flutter and device tooling were unavailable, and actual API keys were intentionally not committed.
