Jetpack-Navigation-Multistack-Example VS android-showcase

If you DON'T actually rely on the multi-stack behavior (1 stack / tab) then there is no need to use NavigationExtensions (personally I wouldn't use them even if I needed that, because the implementation is a bit wonky; you can do more reliable code manually.)

See this sample for auth / conditional navigation then pretend that "ProfileFragment" is the fragment in this sample

I am managing multiple backstacks with Jetpack Navigation just fine in this example https://github.com/Zhuinden/Jetpack-Navigation-Multistack-Example/tree/master/app/src/main/java/com/zhuinden/jetpacknavbottomnavfragmentexample 🤔

Android-Showcase (Android project using Konsist)

In a typical app that fetches data from API (without using Flows), do you prefer to fetch data in a ViewModel constructor (init) or have a dedicated public method called from view (e.g. onViewCreated -> viewModel.onEnter). Here is example of the second approach from the Showcase app (see the onEnter method): https://github.com/igorwojda/android-showcase/blob/main/feature_album/src/main/kotlin/com/igorwojda/showcase/feature/album/presentation/screen/albumlist/AlbumListViewModel.kt

Compose Example App

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.

I think this project is much better for learning as it promotes clean architecture apart from android architecture: https://github.com/igorwojda/android-showcase

Some repos here: https://github.com/igorwojda/android-showcase

That debounce thing is real, no wonder I've seen many sample apps using similar approach to denounce click listener. Do you know why the crash happens?