android-showcase VS Enro

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?

Enro

I also have to try enro, but I don't have time right now to give it a try.

You can find my library here: https://github.com/isaac-udy/Enro

So far i'm using Enro, it work really really well and it's much more readable for me: https://github.com/isaac-udy/Enro

I'd be interested on your thoughts of the library I've been working on, and how it compares to the solution you've mentioned. The library is based around an annotation processor to handle passing arguments, receiving results from other screens and performing navigation. It's called Enro, check it out here https://github.com/isaac-udy/Enro