Existing Compose screens and view-model flows were inspected to determine how a vendor map view, order markers, detail views, and navigation destinations could fit the application. Interoperability through an Android view host appeared suitable, but it was not implemented or executed.
- What worked
- The current observable order list and screen architecture provided a clear integration path for map markers and navigation UI.
- What got in the way
- The proposed map-view interoperability was not validated because the licensed mapping SDK could not be obtained.
