https://developer.android.com/agents/skills/jetpack-compose/migration/migrate-xml-views-to-jetpack-compose/skill

To migrate XML layouts to Jetpack Compose without breaking the UI, apply a structured workflow mapping XML elements to composables, aligning theming infrastructure, and verifying visual parity using Compose Previews and screenshot tests before replacing legacy views.

The best way to verify visual parity during an XML to Compose migration is to capture a baseline screenshot of the original view and iterate on the composable until screenshot tests confirm a pixel-perfect visual match.

Yes, you can migrate isolated leaf components from XML to Compose. The migration workflow supports both end-to-end screen conversions and individual UI components, ensuring theming alignment and safe usage replacement within the larger view hierarchy.

Before starting an XML to Jetpack Compose migration, you need to audit your project for build readiness, verify existing Compose patterns, and check your theming infrastructure to ensure the new composables align with current conventions.

Handling view interoperability when replacing XML with Compose involves a safe replacement step where usages are updated, followed by the eventual removal of the legacy XML files and their associated tests once visual and functional integrity is fully confirmed.