event-emitter VS live-event

If you mean UI events like the events from the Model to the UI, then you can use a sealed class and a Channel or EventEmitter

I can also comment https://github.com/Zhuinden/event-emitter 😛

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

I use https://github.com/Zhuinden/event-emitter for this sort of thing via DisposableEffect(Unit) {

If there isn't multiple screen switches involved, I use https://github.com/Zhuinden/event-emitter

That's why I wrote EventEmitter and never had a problem.

I use BehaviorRelay in place of MutableStateFlow/MutableLiveData, and I use EventEmitter in place of uh, SingleLiveEvent I guess.

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()

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