Lessons Learned Migrating the Maps SDK to Compose
summary
Maps Compose is a Jetpack Compose interop layer that replaces tedious View-based glue by emitting map objects as composable nodes using subcomposition; it provides a Google Map composable plus child composables like marker that add/remove via Compose diffs, a cameraPositionState using standard CameraUpdate objects, coroutine-based animateCamera, and a guarded mapEffect escape hatch to access the underlying GoogleMap for utilities. Limitations: cameraPositionState is one-to-one with a Map and some map-only properties (mapId) are set once at creation.
AI-written summary · about
chapters (12)
- 0:00Introduction and speaker intro
- 1:10Views vs Compose decision
- 3:18Maps SDK interop with Views
- 5:47Introducing Maps Compose library
- 7:52Lesson one: Think declaratively
- 13:53Lesson two: Reuse existing APIs
- 17:06Lesson three: Use Kotlin features
- 20:14Lesson four: Stay consistent
- 22:42Lesson five: Use Compose types
- 24:29Lesson six: Provide escape hatch
- 26:35Limitations of Maps Compose
- 28:42Summary and resources
related talks
36mLessons Learned Migrating the Maps SDK to Compose
41mComposifying Your Not-Compose Code
28mHow easy is it to draw on GoogleMaps using Compose?
36mHow easy is it to draw on GoogleMaps using Compose?
40mGetting started with the Maps SDK for Android
29mReworking a Core Feature: Migrating from XML to Compose Maps
33mMigrating to Jetpack Compose - an interop love story
38mFrom Android View to Jetpack Compose — A Guide to Migrating to Jetpack Compose