event-emitter VS compose-router

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

Compose router

Many complain about Compose Navigation, with good reason, but there are alternatives out there, I use this one https://github.com/zsoltk/compose-router.

I found this library to be a great replacement https://github.com/zsoltk/compose-router. The example contains a login logout state which is exactly what you are asking for.

One thing I dislike about navigation component is the way it handle args. You don't need an arguments parameter because your destination is basically a composable function which can accept parameters (as it is a function). See compose-router.

The Badoo devs are working on this in both badoo/RIBs and also https://github.com/zsoltk/compose-router