AutoDispose VS materialistic

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.

this is the one i use and has widget as well https://github.com/hidroh/materialistic

Anyone know what's happened to the Materialistic HN reader? It was definitely the best Android reader around, and now it's sadly suddenly disappeared.

The Github still exists at https://github.com/hidroh/materialistic.git.

Has anyone forked it or can it be resurrected at all?

https://github.com/hidroh/materialistic

screenshot of me signed in:

HN downweight political stories, what you need is this:

https://github.com/hidroh/materialistic

Particularly the 'Catch up' section.

As a workaround, I have been using Materialistic to browse HN from my Android phone. It has a nice dark theme, which I use by default.

https://github.com/hidroh/materialistic

Yes I love Materialistic as well.

The link problem is also the only annoyance I have. Sadly it looks like many issues have been opened for the bug but I don't see any discussion on the tickets: https://github.com/hidroh/materialistic/issues?q=is%3Aissue+...