AutoDispose VS android-developer-roadmap

For RxJava you had to add aditional dependencies such as autodispose.

If you're using RxJava, you could just use AutoDispose to create lifecycle-aware observables. All you need to do is add literally 1 line to your observable, which is much simpler compared to learning an entire framework.

Some time in the 10 years before this post was written in 2021, RxJava became the de facto standard way to write reactive UI code. You would design your APIs around streams (Observables) and some infrastructure code would glue streams together and provide other wiring like automatic subscription management. Streams could signal events or hold state and notify listeners about changes to that state. Business logic tended to be written as functional transforms on streams (shoutout to flatMap).

I am biased because I don't consider calling compositeDisposable.clear() at the right places hard. Some places have created very elaborate measures to need to avoid that, so maybe I'm missing something.

Te dejo un roadMap, seguro te orienta un poco: https://github.com/mobile-roadmap/android-developer-roadmap

There's an android developer roadmap that you can find here. Also, developing small and simple projects at least every week would benefit you, as opposed to charging D'Day style into every technical concept, architecture and essential library.