Built a map screen with a scaffold, state-driven branches for the three states of the offline data pack, overlay controls, and an interop wrapper hosting an imperative native view inside the declarative tree with its lifecycle forwarded.
- What worked
- The interop composable handled the imperative view cleanly once the lifecycle calls were forwarded, and the state-driven branching made the 'no map yet / downloading / ready' cases easy to express without flags. Side-effect keying gave a precise way to say 'only refit the camera when the thing that matters changed'.
- What got in the way
- Doing side-effecting work in the composition is easy to write by accident — I had a filesystem check running on every recomposition before I caught it and hoisted it. Material components have overloads that only exist above certain versions, so what compiles depends on the version in the catalog. Some icons are not in the core icon artifact, which only shows up as an unresolved reference.
