🤝 Navigation Compose meets type safety. Add compile time type safety to your Navigation Compose screens by using the Kotlin Serialization based APIs available in Navigation 2.8.0-alpha08. → https://goo.gle/44rAMjT Whether you're using the Kotlin DSL to build your navigation graph for Navigation Compose or Navigation with Fragments, this approach to Safe Args leverages the Kotlin Serialization plugin to ensure your code is compile time type safe.
we've been waiting for this! Kudos to the Android team for continuously enhancing the Navigation lib. This feature will help us to catch potential issues early in the development process and leading more reliable apps!
Ankit Verma
2w
Finally here 🙌 🤩
This will improve the way we create navigation 😮
Jassi Sikand
2w
I like this, but isn’t the Parceable class supposed to be a light-weight replacement for Serializable?
Perfect ✨ Why just Serializable? What about Parcelable?
👍
So much better than strings 💙
I've been waiting for this
Muaz Kadan
2w
Better late than never 😌
Android Lead Engineer at T-Mobile| Concentrix Catalyst | Android, AOSP, iOS, Jetpack Compose, KMM,Compose Multiplatform
5dIllegalArgumentException while using nullbale boolean & int in the data class that bounded with NavGraph.. they simply said it is intentional 😂 & keep writing NavType for all custom class which you used in the data class. It has to improve a lot. https://medium.com/@boobalaninfo/assessing-type-safe-navigation-compose-in-android-development-8bd09db244bb