
The #1 destination for all things Jetpack Compose. Keeping up with Android Development is hard. We make it easy, entertaining and rewarding. Made by @VinayGaba
- Tweets492
- Following25
- Followers1.3K
- Likes173
![[–] Zhuinden https://www.reddit.com/r/android_devs/comments/1lmtcwg/xml_vs_jetpack_compose_in_2025/n0aah77/ The XML support is rotting away in Android Studio, and Compose has done the mythical 3 years of development. Navigation-Compose is on its way to being permanently erased. Once Navigation3 is final and out, there will be absolutely no reason to ever touch a Navigation-XML or Uri-based Navigation-Compose again. AndroidX is increasingly a multi-platform implementation, with Android on one side, desktop on the other. Compose for iOS is also being worked on. Meanwhile, Flutter is barely even running in Android Studio anymore. Compose wasn't the responsible decision in 2022-2023, but it may be in 2025. In-app predictive back animations between fragments is the final nail in the coffin for Fragments.](https://pbs.twimg.com/media/GumgqUrXwAAcvNQ.jpg?name=small&format=webp)
ALT [–] Zhuinden https://www.reddit.com/r/android_devs/comments/1lmtcwg/xml_vs_jetpack_compose_in_2025/n0aah77/ The XML support is rotting away in Android Studio, and Compose has done the mythical 3 years of development. Navigation-Compose is on its way to being permanently erased. Once Navigation3 is final and out, there will be absolutely no reason to ever touch a Navigation-XML or Uri-based Navigation-Compose again. AndroidX is increasingly a multi-platform implementation, with Android on one side, desktop on the other. Compose for iOS is also being worked on. Meanwhile, Flutter is barely even running in Android Studio anymore. Compose wasn't the responsible decision in 2022-2023, but it may be in 2025. In-app predictive back animations between fragments is the final nail in the coffin for Fragments.
























