Can someone explain me `navigation-compose` advant...

# compose

[Grigorii Yurkov]

Can someone explain me navigation-compose advantages over simple when (screen) {...}?

@Composable
private fun AppContent(
    navigationViewModel: NavigationViewModel,
    postsRepository: PostsRepository,
    interestsRepository: InterestsRepository
) {
    Crossfade(navigationViewModel.currentScreen) { screen ->
        Surface(color = MaterialTheme.colors.background) {
            when (screen) {
                is Screen.Home -> HomeScreen(
                    navigateTo = navigationViewModel::navigateTo,
                    postsRepository = postsRepository
                )
                is Screen.Interests -> InterestsScreen(
                    navigateTo = navigationViewModel::navigateTo,
                    interestsRepository = interestsRepository
                )
                is Screen.Article -> ArticleScreen(
                    postId = screen.postId,
                    postsRepository = postsRepository,
                    onBack = { navigationViewModel.onBack() }
                )
            }
        }
    }
}

(code from JetNews)

[alorma]

Separation of concerns

From anywhere you can navigate just by call navController.navigate()

instead of depend on a viewModel or similars.

Also, arguments, and deeplinks

[Ian Lake]

We talk about what you get in the release notes: https://developer.android.com/jetpack/androidx/releases/navigation#compose-1.0.0-alpha01