Type-Safe Navigation with the OFFICIAL Compose Navigation Library
HTML-код
- Опубликовано: 14 май 2024
- In this video I'll show you the Type-Safe Navigation with the OFFICIAL Compose Navigation Library!
💻 Let me be your mentor and become an industry-ready Android developer in 10 weeks:
pl-coding.com/drop-table-ment...
⭐ 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/premium-courses...
Get my FREE PDF about 20 things you should never do in Jetpack Compose:
pl-coding.com/jetpack-compose...
Regular programming advice on my Instagram page: / _philipplackner_
Join my Discord server:
/ discord
Get the source code for this video on GitHub:
github.com/philipplackner/Typ... 
Наука
7:17 He sounds so happy about it 😭
yea... I felt that in his voice 😄
😂😂 I felt that too
X3
its like every developer after a new good feature
Cause this feature reduces hundreds of lines of boilerplate parsing arguments, ensuring they're not null, etc...
Yes. Yes. Yes. Omg. Tears of joy. Really needed a new way!!!!!
This is actually the best news in android i've heard in a really long while
I was using Circuit and it's own navigation, so I've been making use of type-safe screens with painless parcelable arguments for quite a while.
It's nice to now see this present in the official library.
Omg this feels much more satisfying to do nagivation straight with classes now. Beautiful update.
Such a relief, I need this to be in compose stable
Wow wow wow.... tears in my eyes as well.
So excited to try this.
It's so easy now. Thank you for bringing this content to us! Keep up the great work, hugs from Brazil.
Philipp, I've no words!!!! Thank you for brightening my day! But mostly thank you for the truly TREMENDOUS amount of work you're doing to bring all those updates to us in a manner that's both timely and incredibly clear. Just... Thank you!!!!
🙌❤️
The demo is a pretty simplistic, but a good intro into the new Nav feature. In the real world you'd be getting the screen argument from savedstatehandle. Keep up the good work Phillipp, your videos have saved me hours. Thank you.
Just wrapped up a project that used a lot of the old compose navigation. Looking forward to this
That JSON serialization is how I did before for passing argument.
Though my approach on serialization & deserialization boilerplate can be ugly.
Agree that it is a great improvement. I wish they made this available since the beginning.
Philip my guy, this is awesome... love all your work
Finally .. a simple straight routing .. 😊
2 reasons why I started and stopped Android dev within a year:
1. Lack of a package manager that handles all package installations, they're dependencies and versions without having to manually do it every time and manually tweaking package and dependency versions
2. Navigation between screens
The second one seems to be solved. If the first one gets solved, I'd be back to Android dev in a heartbeat
Could you please make a video about Drawer/BottomNav using this lib? Especially how you would handle the selected-property of a nav-item (and the corresponding icons)
It was really a big problem for beginners for me to change the screen and you made it easy now
Thanks who created this, thanks Phillips ❤ That's what we're waiting for
Amazing ! I'm already making a PR on my projec with theses improvments 😁
4:03 we can clearly see his happiness.
Finally! As soon as the stable release is out I will implement it.
Thanks philip ,you are really amazing.
Thank you for bringing this content in a very didactic way
Very good, my project is in its final stages. I'm going to take advantage and refactor it to be cleaner. Thank you very much friend.
Thanks Philipp! This is amazing!
Thanks this is helpful. Love your videos.
If you were in tears, I'm crying right now hehe. Love it, thanks a lot!
Good information Phillip ! Thos wpuld really helped my ptoject for compose multiplatform
Finally some good updates, finally so much relief after this update
This looks similar, but even better than Decompose. As always, thanks for sharing these great videos and quality content!
What an improvement!
Highly appreciated 🥳
Aaaaand thanks again for sharing man! 🎉🎉🎉
being as Android Native Developer appreciate 👍 you
Lucky me.. I just started doing compose and KMP, so I haven't suffered like you 😄 I see some cool changes
Amazing, worth sharing
Just use Reimagined Navigation that has a bunch of cool features such as type-safe navigaiton and Parcelable support out of the box. Also community have the Decompose as a multiplatform solution. Both of these libraries are completely driven by community so if you prefer only official libraries it's always OK
Finally we got it!!
I am Big fan of yours video 🎉
Thanks again for that demo. Spot on, as always 👍
Originaly, it seemed that the routing library was made to handle all routes as deeplinks. I wonder how deeplinks will work with that new approach? Should we write a deeplink handler that would reroute the user to the proper screen? 🤔
Finally. Thank you Philipp
Nice. I'll be very usefull.
Thanks to share bro
There was a crash when we try to pass custom type like User(val id: Int, val name:String, val isPremium) in 2.8.0-alpha08 version which is fixed recently in version 2.8.0-beta01.
Thanks for the video. Is the bottom navigation also changing accordingly? What is needed to have screenB with bottom navigation graphs? Thanks.
What if I need this parameters on ViewModel?
It is a really great news !!!
Now we need another navigation video to compare all the options with pros and cons for each 😄
This is awesomeeeeee!!!
Wow this is amazing 🎉
OP gonna start using jet pack compose now
Haha I can relate to your joy about this update so much 😂Great video!
Still nice improvement however the main advantage of f.e. voyager is that you do not need to declare the navHost and its all routes. Voyager allows you to just jump from ScreenA to ScreenB without declaring it in your navHost. Google's navigation is still kinda similar to the fragment navgraph but without the childlish arrowing thing.
Thanks for the video! So exciting! I have a question, does it automatically work with SavedStateHandle in a ViewModel?
I did today and worked well. but you should use the method now like "SavedStateHandle.toRoute" not just "savedStateHandle" in a ViewModel.
excellent just like SwiftUI!!
Finally, FINALLY!
Wow, this really is a lot easier than it used to be
that's great, finally
Great Video!!! How do you retrieve args from the destination viewModel directly? If I use savedStateHandle inside viewModel still needs to safe the possible null argument using ?: or !!
OMG, I wish this could have come earlier. In my first app I have spent so much time and effort just to handle navigation without relying on 3rd party libraries.
I have an e-commerce app running in production with lots of screens hanging on those route strings. It's time to refactor and remove all that boilerplate code.
Need this in KMM!
Так забавно наблюдать, как мои любимые yoytebers выпускают обзоры на новые функции библиотек android и kmp примерно в одно и тоже время и у каждого свое красивое решение использования.
thanks for video. Is this new lib support compose Multiplatform ?
looking forward you make a video about this but with multiple nested graph. im newbie and im so confuse right now.
Can you make a video on how to implement this way of navigation, using a navigation drawer for example or a bottom nav bar?
I once said XML way of navigating was better than Compose. Now it's getting better. 😀
I love you ♥️♥️♥️♥️♥️
You are the best
KotlinX Serialization brings back old memories from 2019
so great
Any tips on naming? I already use FooScreen for the actual composable UI.
The questino is in my view model how would I use savedStateHandle to extract the parameters?
Hi Philip, can you make a video about drag and drop of lazy column, i have stuck there. It seems they have recently added this capability.
Cool update 🤩 what I'm more curious about is that how does recommendations work ? is it an extension or a live template or smth ?
Gemini AI suggestions in Android Studio Jellyfish
Thanks @Philipp Lackner, one thing I have to mention is we can't send empty string as value, I am using 2.8.0-beta01.
With "empty string" do you mean:
1.a text with no characters; like ""
2. or do you mean undefined
3. or do you mean null
@@SunAndMoon-zc9vd I mean "" this
Does this also work with the new kotlin multiplatform navigation or is it only an android feature?
hi! how would i do it if i have 2 UI sets for 2 usertypes? i have a radiobutton on the signup to identify them. how can i navigate them to the right set of UIs i already have my bottomnav that has 5 screens
Damn Thats so good
Pls make more on this
I have purchased Essentials course. Will this be incorporated in the course as well?
isn't that cool? YES it is f cool! Thanks Philipp
So cool and so safe !! But now how i can use deeplink with this serialize data road ?
Is this usable also for KMM?
This is most exciting Compose feature to date imo. Having just finished a Compose app, navigation was the ugliest thing to deal with by a long way.
We can use it in prod apps ? its on alpha or you recommend to use it from now on
How do I reference the object into a navigation drawer argument? I keep getting crashes when I try to use a var to carry the object name into the navigation drawer item. Thanks
Can i use this in production app?
Havent had the chance to play with this yet. How does it deal with deeplinks? And is this implemented for kmp compose?
how to use this with multi module project with feature modules not depending on each other just like android recommends?
with this approach how can we do a shared transition between screens?
is it also available for KMM?
Could you please explain how we can safely integrate vertex AI into the application with Google Cloud Console. I need this urgently.
Clean
Can I use the library normally in kmm?
Is it superior to voyager and decompose?
Finally ❤️
do somebody still wish to work for google and develop shitty frameworks and libs and maybe correct them 2 years later to be somewhat usable? I have the feeling that every dev-product google provides is garbage if jetbrains is not involved in the development
FINALLYYYYYYYYYYYYY!!!
Is there a way to gradually migrate to this meanwhile still keep the current navigation in xml? Simple the current project has large codebase and too difficult to migrate it in one shot.
uffff, finally!!
how does this work on a nested navigation?
Now I will learn it I has paused my learning
I wonder how other libraries (mentioned in the comments) can get use out of Parcelable. For KMP. I thought It was only android thing