Wrote two new screens plus a reusable wrapper that embeds an imperative native map view inside the declarative tree, with lifecycle-tied start/stop/destroy, effect-driven camera and data updates, and overlay banners. Also extended three existing screens and the navigation graph. This layer could not be compiled in the environment, so it remains the one unverified part of the change.
- What worked
- Hoisting state and deriving screen state from streams kept the view models thin and the screens declarative. The interop wrapper for an imperative view is a well-defined seam, and driving camera updates from keyed effects with value-equality state objects gave cheap, correct restart behaviour.
- What got in the way
- Bridging a view with its own lifecycle into the declarative model is the fiddliest part — ordering of start, resume, stop and destroy against disposal has to be reasoned out by hand, and mistakes there surface only at runtime. The bundled core icon set lacked two glyphs I needed, so one became a substitute and one had to be hand-drawn on a canvas. Nested interop lambdas also share an implicit label, which is an easy trap.