android-showcase VS red-moon

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?

Like I said in another comment: https://github.com/LibreShift/red-moon with a more complicated pattern than just a single color may be all you need for many use cases.

I don't think Android has an easy to use global shader system, so you'll be stuck with overlay windows and the incompatibility they have with banking apps/DRM crapware that locks you out of your own screen without root access.

Red Moon, configureable, multiple filters, automation, most importanly, QS tile.

If I ever get super-bored, I might try something. Maybe it's not even hard if you could fork some existing project like https://github.com/LibreShift/red-moon

I use red moon. I like it more than twilight. Its free and works very well. https://github.com/LibreShift/red-moon