Reworking a Core Feature: Migrating from XML to Compose Maps
summary
Migrates Tractive’s map from XML/RxJava MVP to Compose Maps plus a Redux-style controller architecture, replacing bitmap-only markers with a composable pin and a behind-the-scenes Lottie frame marker for animations (capture frames every 2.5%, share two bitmap sizes across markers). Live updates arrive every 5s; position interpolation runs ~300ms with fractional steps. QA uses an 80+ requirement checklist; rollout uses a feature flag and sits at 5% for two weeks while fixing hot issues.
AI-written summary · about
chapters (7)
- 0:00Pet tracking maps intro
- 1:03Original map architecture
- 9:57Compose Map in 2024
- 17:22Benefits of Compose Map
- 18:24New state machine architecture
- 25:29Q&A rollout process
- 27:39Migration learnings
related talks
36mLessons Learned Migrating the Maps SDK to Compose
30mLessons Learned Migrating the Maps SDK to Compose
41mComposifying Your Not-Compose Code
28mHow easy is it to draw on GoogleMaps using Compose?
37mMigrating your app to compose, step 1, live coding
18mCompose Adoption at Pinterest: A Postmortem
36mJetpack Compose: Drawing without pain and recomposition
21mPerformance best practices for Jetpack Compose