How to Pass Custom NavTypes in Compose Type-Safe Navigation - Android Studio Tutorial
Вставка
- Опубліковано 6 січ 2025
- In this video you'll learn how you can pass any type of data class as an argument from one screen to another using the new type-safe navigation framework.
💻 Let me be your mentor and become an industry-ready Android developer in 10 weeks:
pl-coding.com/...
⭐ Courses with real-life practices
⭐ Save countless hours of time
⭐ 100% money back guarantee for 30 days
⭐ Become a professional Android developer now:
pl-coding.com/...
🎁 Get my FREE 4.5h course "The Best Practice Guide to Android Architecture":
pl-coding.com/...
Read our weekly Android blog:
pl-coding.com/...
Regular programming advice on my Instagram page: / _philipplackner_
Join my Discord server:
/ discord
Get the source code for this video on GitHub:
github.com/phi...
Yesterday was exactly two years of my sponsorship of your channel! Thank you Philipp for your videos and especially for the videos from Twitch, which two years ago opened the door to the world of development for me. Developing a full-fledged social network app on Compose with a multi-module clean architecture in combination with a KTOR backend and its deployment to the server is the best thing education material I have ever seen in my life.
🙏❤️
The 2-weeks-old video is just in-time to solve my problem. Thanks a lot.
THANK YOU PHILIPP !!! It works !😃👍
Too bad they did not utilize the serialization fully. Registering custom NavTypes for serializable classess is such a bad design decision.
u are the best, thx for all of u videos
Great and life saver ❤
Great! Philipp, do you have any video showing your Android Studio IDE configurations?
thanks for this video Philipp.
Got a quick question. How could I extract the dog model from the savedStateHandle on the details screen viewmodel?
savedStateHandle.toRoute() ?
So there is no need to use add sealed class NavigationScreens(val route: String) ?
Awesome video, thanks Philipp. Could you also make one explaining how to pass type safe arguments to a nested navigation?
@@Tbijo54 that's should be no different :)
The only thing you need to know for nested destination is that a startDestination can't have argument. That's all.
thanks for this video.
if you can make a video on android auto and automotive os it would be great.
Hi Phillip can you show us how to build an interface for handle navigation actions with the navController in view models, but you know in a way that View Models still being testable, love you videos thanks so mucho
i know this is 1 month old...
but is this still up to date witht the 2.8.1 compose navigation ? (the stable one) or is there an easiest way to do this?
Great video! Can I use it somehow to return result from screen?
the latest navigation release doesn't require the typeMap of enum to be passed.
It is required on beta07 on minified app or it will crash. There is an issue tracker on this and it will be solved in the next version 21st of August.
Awesome One!
Is this custom nav supports to add a screen transition?
Could you please explain how i can pass an argument from DogDetail back to DogList if the DogDetail Screen is finish?
Hi Philipp, you mentioned that one should not use this approach in case of big custom objects because the Bundle has some limits but I wonder why anyone has never highlighted the same before? Like people have been and still use Bundles for passing arguments to Fragments when they create a Fragment's instance. We are using the same Bundle class here too right?
This has been highlighted lots of times that it's better to pass an ID and reload something from the DB rather than passing the whole object. The official docs also suggest that somewhere
I see, need to read the docs about the Bundle limit. Thanks
I would rather save the data in a ViewModel than pass it as an argument (if its large data), What is your take on this ?
Hi @PhilippLackner , How to pass Custom NavTypes in Compose MultiPlatform for Type-Safe Navigation on Android and IOS?
Hi Philipp , rly thank you for this video , thx to you my routing start working . L have one question to you , why you in this code in NavType use Uri.decode and encode ? Why is is important to do it ? Again thx fro the video :)
If we don't use the URI then app will crash if we have some special characters like "?", "/" in params of Custom Type like for image of User can have these, so we need to encode & decode that to string.
How do we do this for hilt-navigation? don't they conflict?
Is there a way to pass more complex types like lambdas ?
Nice explanation ;)
but
on the first hand why does kotlin wt's to do serialisation on navigation , why can't it pass as normal parameter to constructor . fine ;;;;;)
How can I pass sealed class field as a param?
Why my android studio does not recommend autocomplete like yours ? Thanks for excellent content !!!
You can turn on AI completion
@@trungnguyenhuu8184 thank you
How navigate inside bottom navigation menu with type-safe
Just to confirm, I don't think that feature is available for Compose Multiplatform and nor the type safe navigation, for now at least
?
But voyager available :)
Type safe navigation is already available in the last release
@@osisuper98 yes but from what I've tried, it still not available in kmp
KMP is full of hacks and 3rd party libraries written by a guy from Finland. Not yet.
Nice
Could you please clarify how to create nullable custom types? Because I get an error "Cannot cast ... to NavType. Make sure to provide...". I set nullable in all places where it should be and set isNullableAllowed to true, bui it doesn't work
Same problem, did you find any solution?
How to pass view models between screens using this ? Please help
Why would you want to pass viewmodels?
@@malding1 if I have 3 screens, one start screen, one with show details, one with edit details, how can I edit details without passing the view model ?
I recently started learning android, this may be basic
@@Abhigyan103 he has another video how to pass share view models between screens its very good
why `val DogType = object` and not just `object DogType`?
Why we are using @Serializable and not @Parcelize?
It's Kotlin serialization, not Android thing and it's also multi platform supported. I guess they have the support in their mind.
I agree
It's kotlin serialization, not Java serializable
What a mess
DO NOT USE IT
I used compose type safe navigation in my production app, alot of crashes that are not rereducable poped up in the compose code so I was'nt able to use try and catch,crash free users and sessions droped, navigation 2.8.0 is not a stable version if u want to use some type safe navigation just convert your object to json and send it.
Yup, plus 2.8 probably doesn't support parcelize. A lot of work needs to be done on it. That is the probable reason this version has a lot of beta releases.