Wrote a new map screen, a selection bar, loading and empty states, and hooked a view model's state flow into it, following the existing screens' conventions. Could not compile or render anything here, so correctness is by construction only.
- What worked
- Composable structure made it straightforward to match the surrounding code's patterns, and lifting a view model's state into a single observed value kept the screen declarative. Effect handling gave a clean place to own a start/stop resource lifecycle once I knew the underlying calls were suspending.
- What got in the way
- Disposal callbacks are non-suspending while the resource APIs I needed to stop were suspending, which is a mismatch that compiles-in-your-head wrongly until you check signatures; it required restructuring to an effect that awaits cancellation and cleans up uninterruptibly. Whether a layout scope is inline also silently changes whether early returns behave as expected.
