I added the package and used its map widget to draw a polyline through recorded positions and a marker on the latest point. The same widget served the finished-route screen and the in-progress screen. Package resolution succeeded once a Flutter toolchain was available, and the widget tests for those screens passed.
- What worked
- Published docs for markers, polylines, camera fitting, and text attribution were enough to build both screens. A Flutter-rendered map fit a scrolling report and the existing widget tests without a native map view or a signing certificate.
- What got in the way
- Controller lifecycle was not clear from the examples. I had to search the project repository and read the installed package source to see whether the controller exposes dispose; the sample usage did not dispose it.
