voyager VS compose-destinations

If I were to start a project right now, I'd use https://github.com/adrielcafe/voyager although, it doesn't support Web Canvas or iOS yet I don't think.

Voyager has some bugs (apparently SavedStateHandle doesn't work and the PR is open since Nov 24), Appyx is nice but I hear it's laggy (but honestly, everything in Compose is laggy all the time, so if you use Compose, that's pretty standard tbh), I don't know enough about Navigation-Reimagined to tell you, Compose-Destinations is a codegenerator over Navigation-Compose so you drag in Accompanist-Navigation to have basic screen transitions which is pre-alpha tech.

Voyager

https://github.com/adrielcafe/voyager/issues/42 open since January

Yes, I've checked (it doesn't). I've also read AndroidScreenLifecycleOwner's source code, and I don't see a way for it to ever go to the ON_PAUSE state.

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

So it doesn't matter that I have a simpler one, for Navigation-Compose, I say "i don't care what you use as long as it's not Navigation-Compose", you could even use https://github.com/adrielcafe/voyager and it's a much more solid option.

This time is about navigation, when raamcosta ( https://github.com/raamcosta/compose-destinations) in jetpack compose

The biggest help of all by far was Compose Destinations. It takes away all the boilerplate of maintaining your routes. A simple way to not have to create all those routes yourself with placeholders etc, including deeplink patterns and all. It generates all of that for you in a typesafe way. Just check the basic example on GitHub or the dedicated documentation website.

Here is a great solution for navigation in compose. Actually this is what Google should have done in the first place https://github.com/raamcosta/compose-destinations

Compose destinations is another alternative: https://github.com/raamcosta/compose-destinations

Hey, thanks for sharing here. Do you mind sharing how exactly this library is different from this one https://github.com/raamcosta/compose-destinations and why one would use one over the other?

I don't have much experience with conductor, so I'm curious what your concerns about lifecycle is lacking compared to fragments? But if your team already knows that framework I might just stick with views over fragments. I see there is a compose integration if you do ever plan on picking that up with conductor. Otherwise compose makes fragments obsolete and your team already knows conductor. I do agree the navigation story in compose is not mature especially after jetpack compose navigation. But there are other 3rd party libraries like compose destinations or decompose, but would be nice to see something better 1st party.

I can't recommend the vanilla compose navigation from Google, but the community has built others like compose destinations which is pretty good.

Compose Destinations