navigation-compose-typed VS simple-stack-compose-integration

You can use this lib which is build on top on navigation compose https://github.com/kiwicom/navigation-compose-typed. Its strong typed

Official navigation compose but strong typed https://github.com/kiwicom/navigation-compose-typed

I'd personally definitely go with compose only, use androidx.navigation and use this https://github.com/kiwicom/navigation-compose-typed to give me the convenience of not having to make the type safe destinations myself. It's a great middle addition to the library from my experience. Oh and for now you'd also need to bring in accompanist navigation for animation support, but that's very straightforward too.

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.