In the previous articles I have proposed several significant changes to traditional Android development, and there was one last subject left to be explained: how do we avoid using the Android ViewModel. So in Part III we will focus on this, and then I will present an open source sample app that I built to showcase what we have seen in this series, and a bit more.

To better understand the reasons for what we are doing, it is advisable to read Part I and Part II.

Let’s first recall why we want to avoid the Android ViewModel in apps…

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.

Replacing, applying changes

Before getting on topic, knowing memory leaks will help understand part of the article. When we have…

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…

Jordi Saumell

Self-learner Android passionate. Android tech-lead in progress at Basetis

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store