Does Jetpack Compose have anything similar to the NavigationView in SwiftUI? Specifically: traversing deeper into a stack of screens with back button, swipe back to navigate, and of course the slide animation, etc. I know there is

ModalDrawerLayout

but that is more for a side menu..

Integration between Compose and the Navigation Component is under way, feel free to follow along on the issue: https://issuetracker.google.com/issues/161472731

Are there examples of how this component will be used? Like will we be expected to create multiple activities or fragments? Will we have to create any xml for the nav graph?

From the last CLs I saw, I think you define destinations as composable functions, you don’t use activities/fragments. IDK if you need XML to define the nav graph itself though.

There are samples attached to that issue if you want to take a look

@Ian Lake I’m looking here, is there a better place?

Yep, that is what is checked in right now

Thanks @Ian Lake, I can’t wait for the next alpha, it’s a struggle to build a production level app without proper navigation, since it’s so foundational

Navigation already has a Kotlin DSL as an alternative for the XML graph. We use that DSL as the base for the Compose integration, which allows you to define your navigation graph right inline alongside your other Composable code

🙀 Kotlin DSL does not support SafeArgs right? Will it be for the Compose Navigation?

Are there plans to extend NavArgs supported argument types in Compose? Currently we are only limited to primitive types and parcellable + etc, but are there plans to support composable between navigations?

Safe Args is a compile time code gen to based on parsing XML. There's no separate code gen for the Kotlin DSL, but we're still looking at what might be possible or what best practices will be

and I would like to add a question too, will SafeArgs be available for Compose?

We're talking with the Tools team about both the Navigation Editor and Safe Args longer term, but right now both of them are strictly tied to XML graphs and therefore unavailable when using the Compose Kotlin DSL (the same as if you were using the Kotlin DSL in the existing Navigation world: https://developer.android.com/guide/navigation/navigation-kotlin-dsl).

Thanks!