How is everyone handling navigation in their app?

# compose

[Sam]

How is everyone handling navigation in their app?

[Javier]

You can check the official compose samples, looking for routers in GitHub (I think I saw 2 or 3 libs) or waiting for the navigation component

[Sam]

@Leland Richardson [G] was livestreaming and i asked him, he said native navigation integration is a lower priority

[Sam]

so we might not see it for awhile

[Javier]

It is available in the snapshot repository but it doesn't support args.

I don't know what will be its state when they merge the NavArgs PR.

https://android-review.googlesource.com/c/platform/frameworks/support/+/1423769

[Sam]

oh very cool!

[Sam]

are there any examples of usage?

[Javier]

in that PR you can see some related PRs. One of them is for samples

[Javier]

And in the NavArgs PR you can see examples for it too

[Ian Lake]

Yep, coming soon

[allan.conda]

omg! NavArgs for Compose! ❤️

[Colton Idle]

@Ian Lake any reason why we wouldn't just use AAC ViewModels for data that I would typically put in nav args?

[Ian Lake]

A Bundle of arguments have a completely different use case from non-Parcelable data you'd store in a ViewModel. That's true both in the Compose and existing world, with the same guidance for both