compose-navigation-reimagined VS event-emitter

Navigation Reimagined https://github.com/olshevski/compose-navigation-reimagined

Look at how deeplinks are converted into destinations/backstack here: https://github.com/olshevski/compose-navigation-reimagined/blob/main/sample/src/main/kotlin/dev/olshevski/navigation/reimagined/sample/ui/MainScreen.kt. It is all manual in comparison to the official Navigation Component, but I feel it gives developers much more control on the deeplink handling.

Compose navigation reimagined

Using any of the 5 prominent community alternatives is a better approach (even though most people hoping to use the docs as if it was like, written for stable code, will muck around with their apps crashing if the user inputs a & symbol). I have this thing but I'd consider taking a look at https://github.com/adrielcafe/voyager or maybe https://github.com/olshevski/compose-navigation-reimagined

Also, I'll just leave it here: https://github.com/olshevski/compose-navigation-reimagined

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