RxAndroid VS Dagger2

Since you mentioned java, there is RxJava and RxAndroid. Google general recommendation now is to use kotlin coroutines if you're considering writing your app with that.

RxAndroid

Well, as mentioned in the RxAndroid's Readme, it's only Android extensions to RxJava. It makes it easy to subscribe or observe on the main thread or a specific looper. So just focusing on learning RxJava should be enough. You can find many resources for that, here is a compilation: http://reactivex.io/tutorials.html

Project: RxAndroid (Android specific bindings for RxJava) Copyright (c) 2015 The RxAndroid authors. License (Apache License Version 2.0) https://github.com/ReactiveX/RxAndroid/blob/master/LICENSE

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