Dependency Injection with Koin

What is Dependency Injection, and why would we want to use it? In this episode, learn the principles of Dependency Injection, Inversion of Control and testing.

Find out about other popular Dependency Injection solutions, notibly Dagger, and learn why Koin is a better solution.

Learn what Koin is, how it works, and the basic injection method: modules. Learn about the Domain Specific language that Koin uses.

Learn about the sample app, which uses a NASA API to retrieve a daily photo and description and inject resources into your app.

Learn about the NASA API for retrieving the daily photo and description and find out how to obtain your key.

Add the Koin libraries and learn about the existing libraries needed to run the app.

Learn about Singles and Factories, then create a module with the Single & Factory DSL calls.

Add the base url needed for the NASA API. This will be the starting point for injection calls.

Create a logging interceptor to see the requests and responses from the API. This will be added to OkHttpClient.

Create the OkHttpClient class with the builder, set network timeouts, and add a logging interceptor.

Create an instance of Moshi with its builder, which is used to convert from JSON to the model classes.

Create an instance of retrofit using the components created earlier. Add the Base Url, Moshi and OkHttpClient.

Create an instance of our NASA API Interface. This is the class that will be returning the photos and descriptions.

Since the system creates Activities, this episode shows how to add a special class that allows Koin to inject Activities.

Create an AppModule with the DefaultCurrentActivityListener and ActivityRetriever used to inject Activities.

Learn how to start Koin: adding logging, a context and modules. Then learn to register activity lifecycle callbacks for injecting Activities.

Add the NASAAPIInterface to the MainViewModel and call getDailyPhoto to get the photo and give it to the view.

Create DailyPhotoView for showing the photo and description, and retrieve the ViewModel using our Activity injector.

Create a test to test the Koin modules, implementing the KoinTest interface. This will test that our modules are defined correctly.

Set up tests by using the @before and @After annotations to start and stop Koin, and use Koin to inject test fields.

Create tests to make sure all the network singles were correctly created. This will make sure each class was created and set up properly.