migrate-xml-to-composelisted

# XML to Compose Migration Sources of truth: [Migration strategy](https://developer.android.com/develop/ui/compose/migrate/strategy), [Compose in Views](https://developer.android.com/develop/ui/compose/migrate/interoperability-apis/compose-in-views), [Views in Compose](https://developer.android.com/develop/ui/compose/migrate/interoperability-apis/views-in-compose), [Other considerations](https://developer.android.com/develop/ui/compose/migrate/other-considerations), [RecyclerView migration](https://developer.android.com/develop/ui/compose/migrate/migration-scenarios/recycler-view), [CoordinatorLayout migration](https://developer.android.com/develop/ui/compose/migrate/migration-scenarios/coordinator-layout), [Navigation migration](https://developer.android.com/develop/ui/compose/migrate/migration-scenarios/navigation), [XML themes to Material 3](https://developer.android.com/develop/ui/compose/designsystems/views-to-compose), [Interoperability testing](https://developer.android.com/develop/ui/compose/testing/interoperability). ## 1. Migration strategy Migrate **incrementally**; Compose and Views coexist until the app is fully Compose. 1. **Build new features in Compose.** New screens are Compose, hosted by the existing navigation (for example a Fragment with a `ComposeView`). 2. **Build a shared component library** as you go: common composables and the theme in a shared UI module, so every migrated screen reuses them. 3. **Replace existing screens, simplest first** (static