android-oss VS Pontoon

what do you mean dead? https://github.com/kickstarter/android-oss

The kickstarter is all rx all the time and it's b-e-a-utiful: https://github.com/kickstarter/android-oss

Those benefits feel like the benefits I used to get when I'd right apps in the genuinely fully reactive flow, like how kickstarter writes their app. It's the benefits of streams, right?

I've implemented it before in my open source app Pontoon using motion layout. It isn't too difficult to do.

A separate object that's scoped outside of the activity's lifecycle (Singleton, or something like dagger-hilt's @ActivityRetainedScoped), that exposes state to your app ViewModel to consume. Here's an example on how I approached it personally using a media library called exoplayer & a reactive library.

I like to think my pet project Pontoon is well written in some parts. The package structure is a little messy since I was playing around with modularizing the app for making an android TV version. It's mostly kotlin+rxjava2+dagger hilt. The architecture itself is basically mvvm with extra steps. But overall it's a fairly performant app with a complex feature set (in app & system picture-in-picture, custom theming engine). Feel free to ping me about it if you have any questions.