live-event VS simple-stack-ftue-sample

For Android-specific code, you need slightly different configuration of the maven-publish plugin, but I use it in this repo https://github.com/Zhuinden/live-event

For events, I use https://github.com/Zhuinden/event-emitter with https://github.com/Zhuinden/live-event

ok technically I think last time I even used https://github.com/Zhuinden/live-event because I have lifecycle support via fragments in Composables

I've been using this: https://github.com/Zhuinden/live-event

Well I've been using this which is merely a lifecycle-aware wrapper over this, if you're in Kotlin and you are using coroutine stuff then you can also use Channel(UNLIMITED) with receiveAsFlow()

I originally wrote https://github.com/Zhuinden/live-event but you can use Channel(UNLIMITED).asFlow()

I wrote https://github.com/Zhuinden/live-event/ to make it easy but for some reason nobody uses it, they instead copy-paste LiveData> / SingleLiveData from Google even though it's effectively a hack

A simplified variation can be seen in this repo, a LiveData variant with Jetpack stuff can be seen in this repo, my issue with this sample is that as there is no input + debounce + filter + async data load example in it, there is no switchMap (and even for combineTuple, I can use my other helper validateBy here), and those would be key to understanding the difference in terms of expressibility and power...

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