jetpack-autoloader VS android-showcase

I suggest you to use https://github.com/Automattic/jetpack-autoloader. Is simple autoloader that solves most of issues related to conflicts. I have a project where is sued jetpack autoloader and works great, even with yoast seo and other popular plugins :)

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?