datmusic-android VS tivi

I have learned a lot from reading Tivi's code over the years, here's my app using similar libraries & arch datmusic-android

Didn't expect the migration process to M3 would be this much involved. I thought just changing the MaterialTheme would be enough (new color schema/names, all different Typography names, no Shapes yet etc.). But all other components such as Text, Button, Icon, Progress/Slider, Scaffold, Surface need to be replaced with M3 versions..

I'm using it in production in my small music app (source) and I couldn't be happier about it. I was worried about scrolling until I tried release/prod build. navigation-compose and bottom-sheet integration also has some bugs. But we're not far from a perfect UI toolkit.

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.