Skip to main content

Usage of the ViewModelScope

Usage of the ViewModelScope
Based on my last blog post about easy implementation on Kotlin Coroutines,we were also introduced with the CoroutineContext .That was not…

Based on my last post about easy implementation on Kotlin Coroutines, we were also introduced with the CoroutineContext .That was not too hard to understand, but I think there is a lot of code inside a ViewModel . First you needed a Job() , than you needed a CoroutineScope and in the instantiation you needed to specify one default Dispatcher . After that, you needed to keep track of the CoroutineContext corresponding to the ViewModel/Activity/Fragment lifecycle.

Note: If you are not using a ViewModel skip this post entirely.

Current code:

This is not very long code. However, think of every ViewModel you will be having inside your project. So, you will need some refactoring,or not.
This approach looks nice but has some unnecessary code.

Luckily there is another way of dealing with the CoroutineContext , thanks to Google. There is a lifecycle dependency which provides and keeps track of the CoroutineContext without declaring the Job() , the CoroutineScope and canceling on the onCleared() method.

Introducing the ViewModelScope:

Add this in your build.gradle(module app):

Now check how the ViewModel looks:

Of course, the Dispatchers need to be specified. Another thing we must be careful is that when we fire a coroutine tracked by the viewModelScope and we do not specify the thread it is going to run on the main thread. That’s because the viewModelScope runs on the Dispatchers.Main by default.

Happy ViewModelScoping.

Popular posts from this blog

Modularizing your Android app, breaking the monolith (Part 1)

Inspired by a Martin Fowlers post about Micro Frontends, I decided to break my monolithic app into a modular app. I tried to read a little more about breaking monolithic apps in Android, and as far as I got, I felt confident to share my experience with you. This will be some series of blog posts where we actually try to break a simple app into a modularized Android app.

Note: You should know that I am no expert in this, so if there are false statements or mistakes please feel free to criticize, for the sake of a better development. 

What do you benefit from this approach:
Well, people are moving pretty fast nowadays and delivery is required faster and faster. So, in order to achieve this, modularising Android apps is really necessary.You can share features across different apps. Independent teams and less problems per each.Conditional features update.Quicker debugging and fixing.A feature delay doesn't delay the whole app. As per writing tests, there is not too much difference about…

From Gson to Moshi, what I learned

There is no doubt that people are getting away from GSON and I agree with those reasons too. The only advantage GSON has over other parsing libraries is that it takes a really short amount of time to set up. Furthermore, the most important thing is that Moshi is embracing Kotlin support.

First let's implement the dependency:
implementation("com.squareup.moshi:moshi:1.8.0") It's not a struggle to migrate to Moshi. It's really Gson look-a-like. The only thing to do is annotate the object with @field:Json instead of @SerializedName (which is Gsons way for JS representation):

data class User( //GSON way @SerializedName("name") val name: String, @SerializedName("user_name") val userName: String, @SerializedName("last_name") val lastName: String, @SerializedName("email") val email: String ) data class User( //Moshi way @field:Json(name = "name") val name: String, @field:Json(name = "user_name…

Modularizing your Android app, breaking the monolith (Part 2)

This is part 2 of a series of articles about modularizing Android app. If you haven't yet read the first article, you may find it here.

On our first article we just moved some classes outside the application and applied as an independent module. But what if we have dependencies pulled from the application level? This could be a small challenge. First of all, we want to clarify on how are we going to modularize the app. And depending on the previous article, I chose the by feature version of modularization. First of all, let's show some dependencies that are going to be needed in the whole app.

Note: I'm using Dagger for handling dependencies but manual DI or any dependency tool should be fine to understand this part.

So, this is my dependency schema:


Well, it's not that bad, but this isn't what we want to transform to when trying to modularize the app. If you think about it, modules that don't need a dependency, can get it quite easily. For example: A FeatureXVi…