simple-stack VS tivi

As someone who had been using single-activity since 2015 (a'la Flow) and eventually just rewrote the whole thing to fix all the bugs we had with it in 2017, I find it sad that the single-activity approach was questioned not because it was harder, but because people made their own lives harder. And then Google made their lives harder.

I've been using single-activity but with Simple-Stack since 2016 and never deprecated it because Navigation just has these quirks that impede you a lot. I know how to use it but wouldn't really pick it.

This is why we've been using https://github.com/Zhuinden/simple-stack and it was never deprecated. We've been using it for 6 years, I'd say there was a critical bug but it was fixed in 2.3.1...

I mean, we use Simple-Stack because it makes things easier, if it didn't we'd have ditched it long ago https://github.com/Zhuinden/simple-stack

Agreed. I also added support for it 2 weeks ago.

I don't, because we use this and it's better than activities+intents 😅

We've been making single activity apps with https://github.com/Zhuinden/simple-stack and it has been easier than multi-activity.

I still use https://github.com/Zhuinden/simple-stack to this day, although I still use it with fragments.

I have been using Fragments instead of compound viewgroups lately with simple-stack as the navigator for the single-activity, although I need to figure out how to switch to use onBackPressed+onBackInvokedCallback and not just onBackPressed.

You can think of Simple-Stack as a direct successor of Mortar+Flow.

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.