https://coroutinedispatcher.github.io/coroutinedispatcher/images/stavro.jpeg

The Android guy

Room and coroutines testing

My last article covered some simple example about Room and RxJava instrumentation testing code. Coroutines also have great support in unit testing even though todays topic has nothing to do with it. What I mean is that we are not going to cover runBlockingTest this time. Android doesn’t support that (correct me if I’m wrong please) yet. However, I could schedule a topic about that because it really makes me excited.

Room and RxJava testing

When it comes to testing the data layer, we should always have time for that. It’s very important. You lose data, you lose users. Since I really found testing + Room pretty amusing, I thought I should share it with you. Room has already a great support for RxJava or Coroutines. I have used both ways to access the data layer and I was really satisfied with both. So I decided to make a 2-series blog posts with testing in Room with RxJava and testing Room with coroutines.

An early look at Dagger Reflect

When it comes to solving the Dependency Inversion principle, there is no better way then using annotations in the JVM world. However, generating code in compile time has some costs. For example the build time. And I believe this is the only thing dagger can’t do well alone. This is not a bye bye dagger post. This is mostly, obtaining the most out of Dagger. To solve this problem, Dagger-Reflect was written.

Publish your library to JitPack

Once getting inside the open source concept, the idea and desire to publish a library is inevitable. What you need is an idea, or perhaps make a better version of an existing library, or just you need to use some module inside your company for several projects. With the JitPack, you won’t be suffering at all. So how do you do it? For the sake of this tutorial, I’m just gonna make a logging library.

Some quick notes on Dark Mode

The dark mode, perhaps is one of the easiest functionality to implement without breaking literally anything in existing project. However, it has it’s own hidden costs, tricks. Before implementing the Dark mode, what is most important is that your project must be ready for dark mode. What I had: What I wanted to achieve: The setup: The only thing you need to do to get your app ready for dark mode is the themes tag and the AppCompatDelegate class.

How to produce the SavedStateHandle in your ViewModel using AssistedInject

One of my previous article Dagger Multibinding Saved My Time “claimed” to have found the right practice for providing ViewModels without producing a ViewModel Factory for each ViewModel. Apparently, I was wrong. There are 2 main problems with that approach: 1 - I might forget to add a ViewModel in the Map graph. 2 - With the new SavedStateHandle which stays uniqely in each ViewModel I can’t use a generic ViewModel Factory.