event-emitter VS simple-stack-compose-integration

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

Yup, that's why we're working on https://github.com/Zhuinden/simple-stack-compose-integration/ to make it as simple as backstack.goTo(SomeScreenKey(arg1, arg2)) instead of this navController.navigateTo("some/screen&arg1=${UrlEncoder.encode(arg1.toBase64())} stuff. If you are working on an Android app that will always be on Android-only, why would you inherit limitations from Kotlin Multi-platform?

We have https://github.com/Zhuinden/simple-stack-compose-integration/ but the fact that I'd normally prefer to use fragments kinda holds it back

Simple-Stack-Compose https://github.com/Zhuinden/simple-stack-compose-integration

However, it's worth noting that thanks to a guy named @matejdro we are working on a pure-Compose version, in which setup has been reduced to

And ,yes, although not being made for Compose, also Simple stack :)

i'd love to recommend simple-stack-compose-integration but i never wrote this missing link

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

If you're deadset on full compose navigation I'd check out Zhuinden`s simple-stack-compose-integration

I'm almost tempted to use multiple ComposeViews, but I'm definitely not using 1 ComposeView N composables any time soon, even though technically I have the code to support it.