compose-navigation-reimagined VS compose-router

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

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