What's the preferred way of navigating between the...

# compose

[skwalking]

What's the preferred way of navigating between the screens in compose ? (which will not change in near future)

[Colton Idle]

https://developer.android.com/jetpack/compose/navigation

[Michael Paus]

@Colton Idle Only if you want to be bound to Android for ever. If you have an interest in platform independence you should look elsewhere.

[Adam Powell]

I'd venture a guess that any actively developed offering in this space today is likely to see major conceptual and API changes in the next ~18 months to two years. There's a lot of active thinking around navigation right now through the community and I think it's going to evolve rapidly. Features like movable content and animation enhancements add new requirements and remove old limitations, and growing understanding around general state management does the same. Not to mention the UX zeitgeist.

[Adam Powell]

Most projects are best off picking a navigation solution that solves your problems *today*; don't spend time trying to pick a 5-10 year winner here yet

[Scott Kruse]

Haven't used this but looked interesting at first glance if you have multi platform ambitions https://github.com/adrielcafe/voyager

[Landry Norris]

I've been using decompose for a bit, and I've liked its navigation feature. It also provides lifecycle awareness and an observable type (although, I've always found Flow more compatible with other libraries). Plus it's multiplatform.

[Arkadii Ivanov]

You can try Decompose: https://github.com/arkivanov/Decompose