Toothpick VS Dagger2

Just as an alternative, the library toothpick focused on one concept, scopes, much easier for anyone on Android to grasp. You have application scope, activity scope, fragment scope and custom scope. Even while reading this, I'm sure you already understand what each of those represent. Having said that, it wasn't able to solve most of the other implementation complexities beyond better conceptual abstractions.

If dynamic scope dependency injection is of your interest check the, by far (just my opinion please), best DI lib we can currently use in Android/JVM modules for the last 6 years: https://github.com/stephanenicolas/toothpick

Toothpick

There used to be a thing called "releasable references" which was that. It was removed, though: https://github.com/google/dagger/issues/1117

As said in the title, we will focus on the dependency inversion principle and one of its application : dependency injection. For production-ready applications, it would be better to rely on a framework and not implement its own container. For it, the java ecosystem have 3 frameworks available : Spring, Guice and Dagger.

At Reddit, we use Dagger 2 for handling dependency injection (DI) in our Android application. As we’ve scaled the application over the years, we’ve accrued a bit of technical debt in how we have approached this problem.

Confusing. I initially thought someone ported the Dagger DI framework to Python: https://dagger.dev/

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:

Great job, I have been waiting for this feature/fix for a long time https://github.com/google/dagger/issues/2328

Dagger