Getting started with android architecture components and MVVM Part 2- Dependency Injection

Alright lets do a quick recap. If you haven’t already, I suggest you to read the first part linked below.

Getting started with android architecture components and MVVM Part-1

In the previous post we made an app which fetches and displays GitHub repository issues using android architecture components library. Our app follows Google recommended architecture pattern as was described in the Google I/O 17. We divided our app into the following layers for better code responsibility and separation of concerns:

1. View/UI layer
2. ViewModel layer
3. Repository layer
4. DataService layer

In this part we will use Dagger 2 to add Dependency Injection to our app. So let’s get started.

Let’s Begin

But hold on, you may ask what is Dependency Injection and why should we use it in our app? Good question. First, lets define the word “dependency”.

Dependency:

When one component componentX of an application depends on another component componentY, then we say componentX has a dependency on componentY.

As an example if we look into our own app’s classes ListIssuesViewModel and IssueRepository, we see they have composition relationship or HAS-A relationship as in ListIssuesViewModel HAS-A IssueRepository. Hence we can say ListIssuesViewModel has a dependency on IssueRepository. Now we know what a dependency is, let’s move on to understand dependency injection.

Dependency Injection or DI:

Dependency Injection is a technique to “inject” or supply the dependencies of an object from outside. This means an object creating its dependendencies via new operator is strictly prohibited.

Dependency Injection initially appears to be more complicated than it actually is. The first time I read about it, I almost didn’t get it. But with a simple example I got the idea behind it. Let’s take an example from our issues app.

Dependency Injection Example

Without DI: Here is the simplified version of sample code that we wrote in the first part of the post:

Notice that the class ListIssuesViewModel obtains its dependency of type IssueRepository by instantiating its implementation class IssueRepositoryImpl class using new operator.

With DI: The above class when refactored to follow DI would look like this:

Important thing to observe is how object of type IssueRepository is supplied to class ListIssuesViewModel via the constructor. This technique is known as constructor injection.

Note: IssueRepository is an interface. It acts like a contract between ListIssuesViewModel and IssueRepositoryImpl. More on this later.

Dependency injection works well with Dependency Inversion principle. Dependency Inversion Principle is one of the five SOLID principles, which in simpler words says:

Higher order modules (which encapsulate business logic) should not depend directly on lower order modules (which are actually responsible for low level operations like making database calls, or access disk storage). Instead, they should depend on abstractions.

This is the reason why we have IssueRepository interface in our app, so that the ViewModel class only interacts with the actual implementation class IssueRepositoryImpl via interface as a contract. This prevents tight coupling between the two classes thus making the code more modular, testable and easier to maintain. The below diagram will probably make it more clear. We are using pattern similar to figure 2 in the below diagram.

Image source : Wikipedia

Why use Dependency Injection

Although it seems overkill in our simple app, DI becomes quite useful as the code base becomes larger and eventually manually injecting dependencies become painful and error prone. However we will still go ahead and implement DI in our app for the sake of understanding.

This leads us to another question: OK, how do we solve this problem? Here comes Dagger 2 to the rescue. Dagger is the DI framework and library for java apps.

Advantages of using Dagger includes but not limited to:

1. sharing dependencies across different modules.
2. Better testability, easier unit and integration tests.
3. Less code coupling, hence better code maintenance.
4. Scoped instances.

Enter Dagger 2

Lets see how we can implement DI in our app using dagger 2. The main constructs of dagger 2 are:

1. Modules — Modules are the providers of the dependency being requested. To tell dagger that a particular class is a Module we annotate it with @Module annotation. Module class contains methods annotated with @Provides annotation which actually provide the dependencies when requested by other parts of the code via dagger. Modules encapsulate the logic of how to create the dependency objects.
2. @Inject - Annotating a field or constructor with @Inject annotation indicates that part of code is participating in dependency injection. Annotating a non private field with @Inject annotation indicates to dagger that dependency is being requested there. Annotating a constructor with @Inject tells dagger to use that constructor to instantiate the class. Dagger also supports field injection, but constructor and field injections are most widely used.
3. Components — Component interface is like an intermediate that connects the dependency providers (Modules) with the dependency requestors (@Inject properties). In component interface we mention which modules to fetch dependency from and specify which parts of the code would require DI using field or method injection. To create a component, we annotate the interface with @Component annotation. Dagger will generate an implementation of this interface at compile time and the generated class would create the dependency graph. The generated class name will be interface name prefixed with Dagger.

Check the references below to learn more about Dependency Injection and Dagger.

Time to code

We will use Dagger to supply the following classes as dependencies in appropriate places: GithubApiService, IssueRepositoryImpl and ListIssuesViewModel and ViewModelFactory.

First, add the latest version of dagger 2 (currently 2.11 at the time of writing) dependencies to your app level build.gradle file

compile 'com.google.dagger:dagger:2.11'

annotationProcessor 'com.google.dagger:dagger-compiler:2.11'

Lets begin by creating our module class.

Note the annotations used in the above class, @Module and @Provides have been discussed above. @Singleton annotation ensures the class instance as singleton across the dependency graph. We will instantiate our dependency graph in Application class and this will ensure the instances of GithubApiService and IssueRepository will be singleton throughout our app.

Next we’ll create our Component.

Notice how we specify the modules to be used with the component inside @Component annotation. The method void inject(MainActivity mainActivity) tells dagger that we will be requesting field or method injection in MainActivity class.

Next we’ll make some changes in IssueRepositoryImpl and ListIssuesViewModel to support the DI.

@Inject annotation on field mApiService tells dagger that it is requesting dependency of type GithubApiService to be injected. This is the example of field injection. And @Inject above the constructor indicates Dagger to use this constructor to create instances of IssueRepositoryImpl using this constructor when the dependency is requested. Doing so also adds this class to Dependency graph.

Here everything is similar as described above, but the only thing to point out is that because the constructor annotated with @Inject have a parameter of type IssueRepository Dagger will try to supply this dependency as long is also exists in the Dependency graph.

All seem to be good so far. But we have a situation that needs attention. In the previous post we briefly mentioned that if a class extending ViewModel class has a non empty constructor we would have to write a factory class which would implement android.arch.lifecycle.ViewModelProvider interface. This factory class class would be responsible to instantiate our ViewModel class.

In the above code we add ViewModelFactory to the dependency graph and dagger will handle injection of ListIssuesViewModel in this class. In the create() method we return the obtained instance of ListIssuesViewModel.

Next we’ll create IssuesApplication class which we will use to initialize dependency graph for our app using Component.

Don’t forget to add property android:name=".IssuesApplication" to the <application> tag in AndroidManifest.xml file.

Finally we make changes to our MainActivity.java file:

In above code we first get the reference of our component DaggerAppComponent from the Application class and inject the MainActivity so that it can take part in dependency injection. ((IssuesApplication) getApplication()).getAppComponent().inject(this) is necessary here since we don’t have control over the creation of MainActivity (hence we can’t use constructor injection technique), so this is how we ask dagger to include it into our dependency graph. This enables us to inject our ViewModelFactory here and supply it to ViewModelProviders.of() method, which tells architecture components library to get the instance of ListIssuesViewModel.class from our factory class.

So now we have Dependency Injection implemented in our app. I hope that I am able to get you started with the idea of DI and highlighted the reasons to use it. If you have any doubt or any suggestions for improvement or errors, feel free to reach me out.

The full code for this tutorial can be found in GitHub repository in branch named “mvvm_part2_di” . And don’t forget to star the repository.

If you liked this article, please recommend it by pressing 💚 button.

References

1. YouTube video by Gregory Kick: DAGGER 2 — A New Type of dependency injection

2. YouTube video on DI by Dan Lew: Dependency Injection made simple

3. Dagger 2: official page

4. Codepath: tutorial on Dagger 2

5. And last but not the least, google’s excellent: sample app for architecture components demo on GitHub

Originally published at shahbaz.co on June 10, 2017.