Since the release of Retrofit2 version 2.6.0, there has been added native support for co-routines, this helps to achieve better performance and reduces boilerplate significantly. I will show you how to change/implement your repository, view model and the UI controlling activity. Finally I will show you how to handle errors with this new approach.

The main changes that you will need to make is making the co-routine calling functions suspendable, as is required for them to function in their intended manner, i.e by stopping and starting according to the application state.

So in our API interface we make the @get function a suspend function as shown

Next comes the Repository class which creates the instance of the retrofit service and initiates the API call, our method for this call should be a suspend function as it will later be called through a co-routine.

As you can see the code which was earlier 50–60 lines has been reduced to a very clean single line, as the procedure has been streamlined through the use of a co-routine. The main thing missing from the getData() method is the error handling callback that is automatically created when a call is enqueued.This error can be handled by wrapping the co-routine in a try/catch block. Now that our repository is set up we can create a method in the viewModel which uses the liveData builder to create a process on the IO thread.

Add this viewModel and liveData dependencies for the coroutine to work

• implementation "androidx.lifecycle:lifecycle-extensions:2.2.0"
• implementation "androidx.lifecycle:lifecycle-livedata-ktx:2.2.0"
• implementation "org.jetbrains.kotlinx:kotlinx-coroutines-android:1.3.0"

The emit function emits the changes in the underlying database to the observer variables, in our case which will be located in the MainActivity.

Here we can see the observer observing the value of aqi from the API and updating the UI accordingly.

That's it! your code has now become significantly cleaner and you have leveraged the power of co-routines.