Has anyone tried to use navigation in compose mult...

# compose

[Jannik]

Has anyone tried to use navigation in compose multiplatform? I looked it up and it is recommend to use Voyager or decompose, however if I add it in the gradle build file it isn't recognised

[Anum Amin]

I have worked with Decompose, and it works perfectly fine

[Jannik]

Does it also have wasm support? I tried using Voyager which doesn't really work:/ thx for the fast reply

[Anum Amin]

I never tried with wasm, but as per the doc it supports wasmJs

[Anum Amin]

How good the support is, you need to explore that

[Jannik]

Will do, thanks a lot!

[Arkadii Ivanov]

Decompose supports Wasm for Browser since version 3.0.0-alpha01.

[SrSouza]

Voyager, hopefully we will have a version in two weeks with WASM support.

[Mark]

@Anum Amin yeah, as someone who is currently looking into both voyager and decompose, my only concern about voyager is there seems to be very little noise surrounding it, and also not much in the way of support.

[Anum Amin]

I am not sure if it's true. But Voyager is meant for compose multiplatform only, while Decompose supports both native UIs and compose multiplatform.

[Mark]

Hmm, interesting. Any examples of what native Android UI functionality Voyager does not support?

[Anum Amin]

Its about multiplatform navigation support rather than native android UI. Also, since I never explored Voyager myself, therefore I will not be able to answer it

[Arkadii Ivanov]

I think this is because with Voyager we directly override a Composable function in screen classes. In this case I think we can't use e.g. React on Web, or SwiftUI on iOS with its native navigation gestures (aka NavigationStack).

[SrSouza]

Voyager uses the Compose composition to do all the navigation events, we have a StateStack (similar to StateList of Compose), that each changes, recompose where is being used inside a @Composable.

[Mark]

This is all very interesting. I’m looking for reasons to choose Voyager or Decompose. My app is currently Android-only with a view to using KMP further down the line. Any examples of what native Android UI functionality Voyager does not support?

[Arkadii Ivanov]

Voyager supports only Compose UI, plus you should be able to insert Android views via AndroidView.

[Arkadii Ivanov]

There are also other criteria to choose one or the other: different API, different feature set, etc.

[Mark]

Hmm, I’m already at the point where my entire Android UI is in Compose, so that part isn’t an issue at least.

[Arkadii Ivanov]

In this case I would check both libs and choose the one that suits my needs more. 🙂

Plus there is also Decompose-Router, which is kinda a simplified compose-first version of Decompose.