No more String-based Routes! New Compose Navigation Release 

For a custom data type we should override one more function in the NavType to avoid that run-time exception: serializeAsValue() and just return Json.encodeToString(value) ✅

You always find amazingly good content. Thanks for the effort you put into teaching us something new. My day is perfect when it starts with your videos. Thank you.

I'll wait to see the stable one, this is really amazing

I always use a navigation viewModel to hold the data( also complex objects) and then read it from the destination screen. Use enum classes to define routes to overcome typing errors. This approach with compose navigation works well in every scenario.

your video is amazing. Thank you so much for sharing this new technology with us.

can't wait to test it out. it's been a long time especially because we already have type-safe in xml navigation

finally!!!! it was a giant pain in the ass for me! it's time for refactoring!!

Thanks you for the video my friend.

Nice update ✌

Currently I'm taking Your course on Udemy ToDo App with Compose, and these string-based routes were strange to me. What a perfect time for this video to come out 😅

Can you make a video about explaining all the effects (like LaunchEffect and all)

The new safe args navigation doesn't seem to work with deeplink.😢

They are adding @Serializable and @Parcelable both to a class ? i was under impression parcelable can improve app performance over serilization.

Can we still get runtime args from SavedStateHandle in viewmodels?

it's also work with Parcelize ?

1:38 Is it possible to replace its sealed class Screen with a sealed interface Screen?

Can you access the argument in the viewmodel?

Wow 🎉

Can you say what the better this navigation or voyager

I tried and faced the similar crash.

eventually :)

I suggest you change the title of your video to include words navigation so its easier to find later!

Bro still basic ui components are (Experimental) and has bugs for 3 year still they dont care it ? And why they still making shitshow apis intead of fix experimentals and stable it. Imagine getting type safe arguments after 3 years.I really dont understand them

Try flutter and make difference video

first

Isnt it more convenient to convert custom object to Jsonstring and pass as string param then parse the 'Json to object instead of creating navtype boilerplate code? Pass Gson().toJson(yourModelClassObject) in string param, then for getting it use generic function: inline fun String?.parseJsonString(): T? { return try { this?.let { val type = object : TypeToken() {}.type Gson().fromJson(it, type) } } catch (e: JsonSyntaxException) { Log.i("Error", "Failed to parse JSON string: ${e.message}") null } } val screenA = it.toRoute() val data = screenA .jsonstring.parseJsonString()

val coverNavType = GenericNavType(Cover::class, Cover.serializer()) class GenericNavType( private val clazz: KClass, private val serializer: KSerializer ) : NavType(isNullableAllowed = false) { override fun put(bundle: Bundle, key: String, value: T) { bundle.putParcelable(key, value) } override fun get(bundle: Bundle, key: String): T? { return if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.TIRAMISU) { bundle.getParcelable(key, clazz.java) } else { @Suppress("DEPRECATION") bundle.getParcelable(key) } } override fun parseValue(value: String): T { return Json.decodeFromString(serializer, value) } override fun serializeAsValue(value: T): String { return Json.encodeToString(serializer, value) } }