Romain Boisselle

Dependency Injection has become boring in Kotlin Multiplatform projects. Now compiler plugins can make the use of this pattern exciting again! Kotlin Symbol Processor (KSP) brings the fun back and helps us manage our dependencies with a nice fully typed API. Let's deep dive into it and see how it works.

In this presentation we will talk about what makes Compiler plugins useful. How they help us build more reliable applications by reducing boilerplate and generating robust APIs.

How we generate code and why can be confusing or misunderstanding. So, we will take Dependency Injection as an excuse for our Kotlin Symbol Processor tour. First of all, we will configure a new processor module. Then we will see how we can create our own Kotlin symbol processor to enhance our architecture by providing a fully typed Dependency Injection API.

Dependency Injection is a complicated topic, and when used in a project that compiles to multiple targets through different compilers & runtimes, it can lead to serious headaches. However, the Inversion of Control pattern brings a lot of architecture features and safety.

In this talk, we will see how to use all the power of Kodein-DI, a popular dependency injection library that works everywhere Kotlin can compile to, in a mobile multi-platform project targeting Android, iOS and the mobile Web.

We will start by using the dependency injection pattern to abstract and test the behavior of multi-platform business modules. We will then see how to debug common dependency management errors.

Finally, we will enhance our common code using advanced features of Kodein-DI such as set bindings, lazy access, context, and scopes.