Lessons Learned Migrating the Maps SDK to Compose
summary
Maps Compose is an open source interop layer that replaces ~100+ lines of AndroidView boilerplate with composable nodes, using subcomposition and a custom applier to add/update/remove markers, polylines and polygons directly from the composition. It reuses Maps SDK types like CameraUpdate while exposing Compose-first types such as mapProperties and mapUISettings, drives camera movement via cameraPositionState (suspending animate), offers a mapEffect escape hatch, and notes limits: GoogleMap stays stateful so one cameraState per map.
AI-written summary · about
chapters (7)
- 0:00Lessons Learned Migrating the Maps SDK to Compose
- 9:35Think declaratively in Compose
- 16:05Reuse as much as possible
- 20:20Use Kotlin features
- 23:41Stay consistent with Compose Toolkit APIs
- 27:04Use Compose common types
- 28:59Provide an escape hatch
related talks
30mLessons Learned Migrating the Maps SDK to Compose
41mComposifying Your Not-Compose Code
28mHow easy is it to draw on GoogleMaps using Compose?
29mReworking a Core Feature: Migrating from XML to Compose Maps
36mHow easy is it to draw on GoogleMaps using Compose?
40mGetting started with the Maps SDK for Android
37mMigrating your app to compose, step 1, live coding
33mMigrating to Jetpack Compose - an interop love story