In part I we saw how, with Compose UI, we can (should?) get rid of Fragments, Android-ViewModels, and configuration changes to make Android development easier. Here we will see how to apply those changes, so make sure you read part I beforehand, to understand why.
As this series focuses more on architecture and the Android framework we will not discuss how to build the UI, theming, or material components. The main focus will be on not using Fragments and manually handling configuration changes.
Jetpack Compose is the new Android toolkit that will change how we build the UI of our mobile applications. Since it was built as a UI framework, there are a lot of posts and talks that focus on how it works internally, and on how to use it to build UIs. However, in building an application there is much more than the UI, and Jetpack Compose can bring a lot of change there too. For that reason, in this series I will focus on several changes that might happen to how we build apps in the future, and for the…
Self-learner Android passionate. Android tech-lead in progress at Basetis