anvil VS koin

Handling DI at scale can be a challenging task in avoiding circular dependencies, build bottlenecks, and poor developer experience. To solve these challenges and make it easier for our developers, we adopted Anvil, a compiler plugin that allows us to invert how developers wire, hook up dependencies and keep our implementations loosely coupled. However, before we get into the juicy details of using this new compiler plugin, let's talk about our current implementation and its problems that we are trying to solve.

In terms of of what Anvil is I'd really recommend reading the README It's a lot more flexible than Hilt and provides a code generation hook so if you have a codebase specific DI pattern you can also set that up to be auto-generated with a custom annotation if you desire.

Recently I've been looking into Anvil as an alternative to Dagger and realised that it can handily generate factories for you without kapt. That brings some exciting potential for build time improvement so I was eager to try it out. However very quickly I got stuck.

I'm currently using Dagger and Anvil for my DI needs. It's been working really well, especially around what Anvil permits in terms of multibindings defined on the type declaration rather than in a module. For example:

Might want to tell koin that : https://insert-koin.io/

To use the viewModels across all screens I use dependency injection by Koin. However Google promotes Hilt, I think that is the golden standard at this point. Both frameworks support creating viewModels with a navigation back stack entry as viewModelStoreOwner.

New modules allow you to easily build KVision apps with the Ballast opinionated application state management framework. You can see how Ballast (together with Koin) can help you design your application architecture in the new todomvc-ballast example.

I started looking into using Kotlin/JS, and hopefully reusing a bit of code that I have, which is using Dagger and Anvil - which of course are JVM only. So I've been looking for other solutions, namely Koin and Kodein. Koin's multibinding support is... not really amazing (e.g. here, and while Kodein does support multibinding, it doesn't seem to support things like that at the declaration site - everything needs to be specified in a "DI container" (module).

Koin

Now I will finish up saying Hilt is just an opinionated way to dependency injection on Android, but there are simpler frameworks out there such as Koin or Kodein that can help take away a lot of the troubles that can come when you try to make your own framework. Just know that most other frameworks tend to be runtime injection instead of compile time injection like Hilt, which can be helpful to know at compile time if you are missing a dependency in your graph as opposed to runtime when its out in the wild.

I've been using Angular a lot and I like how it works. I'm also a huge fan of koin for kotlin.

for injection, I suggest Koin (https://insert-koin.io/)

It'd be great if it worked

For DI take a look at Koin. It's a pragmatic lightweight dependency injection framework for Kotlin developers with multiplatform support. PeopleInSpace sample project uses it.