Update navigation library and refactor the navigation of template to reflect with new style

[kaungkhantsoe]

Issue

Previously, with the old navigation library version 2.7.*, we used to navigate using route strings as follows:

object Splash : BaseAppDestination("splash")

composable(AppDestination.Splash) {
            SplashScreen(
                ...
            )
        }

Solution

With the new navigation library version 2.8.*, we can navigate using as follows:

@Serializable
data class Profile(val name: String)

val navController = rememberNavController()

NavHost(navController = navController, startDestination = Profile(name="John Smith")) {
    composable<Profile> { backStackEntry ->
        val profile: Profile = backStackEntry.toRoute()
        ProfileScreen(name = profile.name) }
}

As you can see, there have been major changes in navigation and passing parameters between destinations.

For more information, please visit the following links 🙇

• Navigation with Compose
• Design your navigation graph
• Navigation library version 2.8.0 release note

Who Benefits?

Android developers

What's Next?

[hoangnguyen92dn]

There are some aspects we should consider for the migration 💡

Previously, we created the AppDestination to handle these things:

• Navigation argument with NavArgument
• Parcelable Argument -> This can be deprecated from our current approach since the new nav compose already support this ✅
• Send result back and forth between screen -> We need to assess this for particular or full migration.