Pontoon VS tivi

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.

Look no more: https://github.com/chrisbanes/tivi

It's definitely the most verbose part of our app and one of the weakest parts of the Jetpack library. We used https://github.com/chrisbanes/tivi for some inspiration on how to organize your navigation structures.

I have considered a few variants around this route. One easy way out would be just to launch a ComponentActivity with a PreferenceFragment like what Chris Banes does in TiVi ... but if you go with PreferenceFragment(Compat) it seems you are kinda stuck with SharedPreferences. If one attempts to supply DataStore wrapped in PreferenceDataStore, it seems types get messed up (TextPreference will store as a String, even if the InputType is number, etc).

Thanks I think what's confusing is that UI events are recommended to be modeled as Flows, which I guess is why Tivi uses Flows for even the simplest actions, but it does a lot of very fancy things. Most repository interactions seem to have an entire class extending an Interactor (e.g.) which catches and emits errors, progress and handles timeouts and does all that crazy queuing stuff with UI "messages" Flow

I would read and study nowinandroid and tivi apps.

Check out the approach from tivi https://github.com/chrisbanes/tivi/blob/main/app/src/main/java/app/tivi/AppNavigation.kt as an idea.

They probably want you to do a module split like in https://github.com/chrisbanes/tivi or https://github.com/igorwojda/android-showcase, but what they probably don't realize is that modularization is a trade-off, namely greatly increased build configuration complexity for... well, having modules.