A modern programming language that makes developers happier.

kotlinlang

Hi, is there a trend what *navigation library* to use. I'm currently using `compose-router` which is relative outdated. It feels like in the long run there will be only `navigation-compose` . I would be fine with switching to navigation-compose, but would like to hear some thoughts and feedback

I don't know about the trend, but I use navigation-compose. Are there any compose-router features navigation-compose doesn't have?

One thing that I mentioned previously is that it is a level playing field - if you like a different navigation library, that's totally fine and they'd have access to the same set of underlying Compose APIs as Navigation Compose: <https://kotlinlang.slack.com/archives/CJLTWPH7S/p1613179206361900?thread_ts=1613159019.352800&amp;cid=CJLTWPH7S>

For multi-platform <https://github.com/arkivanov/Decompose|Decompose>

Yep, Decompose was actually what we were talking about in that other thread

<@U01FRMAHXT2> no, I think navigation-compose does its job well. The main reason why I didn't already switch is the fact that it stacks onto the origin navigation library. It feels like I get a library which navigates in compose but also in views while I would expect a library which only navigates in compose <@UJBPFB3SN> or am I wrong? Decompose... I'm not sure if I like it but I might give it a try.

Well, I don't use views directly. I don't know what happens the level below compose, but there are no views in my code. I have one activity and setContent there for an app Composable.

Same for me... I'm not using views. I just mean that the library is a wrapper around the jetpack navigation library so navigation-compose has an internal dependency on the jetpack navigation library but that isn't a problem at all. Just saying that ypu get more as expected

<@UHC7RPRTN> the problem is Navigation Component library is not available as multiplatform library

I'm not coding for multiplatform :slightly_smiling_face:

And I currently see that Navigation Compose depends on ViewModel stuff which I also don't use anymore.

<@UJBPFB3SN>
&gt; Yep, Decompose was actually what we were talking about in that other thread
Can you please link the thread here. I would like to have a look

Just for reference, `navigation-runtime` is the generic core for Navigation. It doesn't depend on views, fragments, compose, or anything. It is totally agnostic to any type of `Navigator`. Navigation Compose is a compose specific layer on top of that agnostic core that knows how to navigate between composables (just like `navigation-fragment` , a totally separate artifact, knows how to navigate between fragments)

That agnostic core also means you get deep links, returning a result APIs, testing support, back stack integration, saving of state, etc. as part of that package

&gt; I linked it above already?
Upsi my bad.
&gt; Just for reference, `navigation-runtime` is the generic core for Navigation.
ok cool, good to know.
Thanks for your thoughts guys!