AutoDispose VS RxRelay

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.

BehaviorRelay is really good

RxJava with RxRelay (and rx-combinetuple-kt)

Spoilers is that I just store every variable in their own BehaviorRelay.

interesting approach; are you referring to the RxRelay library? do you exclusively use that/RxJava APIs for async work/reactivity in the business domain/data layers as well?

Although generally, just don't use subjects ever, use https://github.com/JakeWharton/RxRelay instead

RxRelay + Rx-CombineTuple-Kt (+ Rx-ValidateBy-Kt) are things I use in my everyday life