Skip to main content

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. What this tool does, is basically moving Dagger a step forward, from code generation at compile time, to code generation at Runtime, which basically is what reflection does, overall.

To set up Dagger-Reflect is pretty easy. Just add these lines to your build.gradle (module app) file:

You can check the docs for full or partial configuration. One thing that doesn't go well with this configuration is repetitive code if you have a lot of modules. Yes, you have to do this in every module that you have dagger. Therefore, there is already a plugin which handles that, and requires only a small configuration from you. Just add these lines of code in your build.gradle (module project) file:

Another small step is to add dagger.reflect = true , in your and you are good to go.

The usage of Dagger-Reflect is pretty simple. Instead of DaggerMyAwesomeAppComponent.factory().create(this), you should add DaggerReflect.factory(

Notes to keep in mind: 
1- Your component must have a builder or a factory.
2- If you have annotations like @Qualifier (in my case, I don't) must have the runtime policy @Retention(RUNTIME)
3 - Should apply the reflection for every component in your application (In my case I have only one component)

Here is the result for the build time:

For more components, the difference might be greater. Imagine with multi modules and a lot of components each.

Why and how?
Dagger doesn't really generate the dependencies at compile time. If we notice, instead of new instances coming out of the DaggerMyAwesomeAppComponent, it's just 2 methods:

Some words about Proguard: You should apply Proguard rules, when full reflection is applied. But I'm not yet in production using Dagger-Reflect because I think it's to early. The current version is still 0.1.0.

As a code generation at compile time fan, i just jumped to code generation at runtime fan. I'm really interested to know how this kind of projects work. I have already forked Dagger2 in github and I hope I find some free time to study how it is done.

Best of luck!  💪💪💪

Stavro Xhardha

Popular posts from this blog

What I learned from Kotlin Flow API

I used to check the docs and just read a lot about flows but didn't implement anything until yesterday. However, the API tasted really cool (even though some operations are still in Experimental state).Prerequisites: If you don't know RxJava it's fine. But a RxJava recognizer would read this faster.Cold vs Hot streamsWell, I really struggled with this concept because it is a little bit tricky. The main difference between cold and hot happened to be pretty simple: Hot streams produce when you don't care while in cold streams, if you don't collect() (or RxJava-s equivalent subscribe()) the stream won't be activated at all. So, Flows are what we call cold streams. Removing the subscriber will not produce data at all, making the Flows one of the most sophisticated asynchronous stream API ever (in the JVM world). I tried to make a illustration of hot and cold streams: Since I mentioned the word asynchronous this implies that they do support coroutines also. Flows vs…

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…