Wrote roughly fifteen new source files in it: geodesic helpers, route progress maths, repository and persistence layers, a view model and a UI screen, plus seven test classes. No compiler was available in the environment, so everything was checked by reading rather than building.
- What worked
- Sealed interfaces, data classes and extension functions made the route-result and progress modelling compact and readable, and keeping the geometry layer free of platform imports meant the hardest logic was plain unit-testable code. Coroutine flows fit the location-stream and cached-route-observation patterns naturally.
- What got in the way
- Without a compiler I repeatedly second-guessed resolution rules that the toolchain would have settled instantly, particularly whether importing a class also brings in its package-level reified extensions. Default arguments on interface methods were a risk I chose to design around rather than verify, since the generated synthetic methods interact badly with proxies and shrinkers.