This library is amazing, but what's even more amazing is what Rafael used to create it. Kotlin Symbol Processing or KSP is "an API that you can use to develop lightweight compiler plugins. KSP provides a simplified compiler plugin API that leverages the power of Kotlin while keeping the learning curve at a minimum. Compared to kapt, annotation processors that use KSP can run up to 2 times faster. Also, because KSP traces symbol resolutions dynamically, a change in a file is less likely to pollute other files and therefore the set of files to be reprocessed is smaller (that's why it's faster). This is not possible for kapt because it delegates processing to javac. KSP can process Java sources as well. The API is unified, meaning that when you parse a Java class and a Kotlin class you get a unified data structure in KSP." So when you mark your composables with @Destination just know that is the power of KSP not kapt.

Finally something like this has been released, thanks for sharing!

Thanks for sharing this Philip! I watched your videos using Compose navigation and was disappointed how ugly Navigation had become. It was a step backwards. You didn't make fun of it in the videos, so I thought it was just me. :-) This is beautiful (thanks @Rafael Costa)

Nice, I actually used his approach in my live streams (without the library tho) Thanks again to Rafael for his help!

What a great library makes the work easier and cleaner Thanks 👏

Thank you Philipp for making this video, and thank you YT algorithm for recommending it to me! At least that's one thing Google did correctly...

Thanks Phillip for sharing.

Yeah not able to pass parcelables were such a pain

Awesome library. I have been using this. 👌🏻

Thank you a lot!

Great, thanks 🔥🔥🔥

very cool library thank you

This looks amazing! Not being able to pass an actual object through the route was such a strange thing to discover coming from SwiftUI and Flutter. Will you migrate to this in your Android Twitch Network series?

Damn Man Rafael u r an angel What a solution ❣

Do you use still use this library in your projects? It's been a year now just wondering

wow this is super cool, now one can pass actual objects!

I am unable to generate the classes after rebuilding the project. how can I resolve this problem?

Rafael is genius.

Hey, Philipp! Thanks for this amazing video. Has Google come up with a better solution as of yet? Or should we use this 3rd library?

can we use this in bottom navigation?

how to implement nested navigation graphs in this library?

👏 Amazing, you are a life saver

great, but could you make a bluetooth example with compose by any chance?

It does not identify "NavGraphs.root" in "DestinationsNavHost(navGraph = NavGraphs.root)" anymore. Any help please?

Is that library can support nested navigation?

Hi Philipp, Have followed the lecture but I am wondering if you use Compose Destinations, where does that leave the theme?Since you have moved the screen composables out of the Main Activity, how then do you theme the app?

How could I implement a navigation drawer or bottom navigation using this library 🤔

what is the name of the theme you use in the IDE

You made my day ✊✊✊👍👍👍

What an amazing library. I love it, I just have one concern. So, I was told before by boos not to use third party library for our app (which is a release app published on store) because incase one day support stops for such library then our app will not be functional anymore. So, what are your thoughts about this subject using this library? Like, is the library dependable enough to use in released apps? or I should stick with native compose? Your replies are much appreciated!

Can we still get navigation arguments from saveStateHandle in view model like in compose navigation?

thanks so much

that would be awesome if you talk a bit more about back Stack. yeah great video btw

Wooow this is amazing

Maaan, this library is legendary !!!

Could you please make a video on how we can add the transition to this library?

Thank you for the amazing video!! could you please do a video about how to use this navigation library with a top app bar (with dynamic titles and icons) 😢

Thank you very much , but we need you to make a video of Bottom Bar navigation with this awesome library (raamcosta )

How would this library work with bottom navigation and can it prevent 1 screen from stacking up if reselected repeatedly?

sir hwo we use this with bottom navigation

Awesome !! Could be nice to check how this library can work along with accompanist-navigation-animation :-D

How can we implement this with Bottom Navigation Bar? I tried something but as soon as I press a button in Bottom Navigation Bar, whole screen, including the Bottom Navigation Bar, is changed to new destination.

omg thank you so much

How can we override Deeplinks?

I love this..my only confusion is wether i should start learning and using this right away..or perfect the previous way first..is it advisable to learn the previous way first or i should jump right into this..? Any help is appreciated.

Why doesn't "Join" button appear on my KZfaq app?

Is conditional start destination possible? For example Non auth. user - after splashscreen immediately goes into login/register destination Authenticated user - splashscreen stays visible while data is being fetched and then user is redirected to Home destination. It was a bit tricky for me to get this working with xml nav component and the splashscreen api, but at the end it turned out quite good. So I'm wondering if I can easily migrate this part to compose.

Chris P Bacon, lol. The lil pig. W reference

Why not use this library in newest video..?

Super cool

Epic. But can i use this library if I'm developing app where i don't want the code to be open source?

finally you changed the theme

Hi Philip Have you ever manage to do a mix match with the conventional google navhost or with this KSP one , to have a bottonsheet modal support , without crashing the app due to 2 different navhost has different startDestination, I get like an error like this"ViewModelStore should be set before setGraph call"

hey philip thanks for video also could you make a video about to modular architecture

Looks great, however what if I want to share a viewModel between destinations?

hello there .. your tuts are amazing .. can i request to make a full jpc apps with multi modular please ?

Incredible

any idea, how to pass `arguments: List` and `deepLinks: List` to the navhost composable with this library

Hey, can you tell which theme you are using? 🤩

How to give viewModel as argument to root screen. I have a screen which contains navDrawer and I want to navigate to other screens inside the content of navDrawer.

Great video! How can you implement a conditional startdestination?

Does it affect performance negatively? If not, then it's incredible!

This is the second most awesome thing I've ever seen.

How about animations between screens? Thank you!

How do you pass in a DestinationsNavigator for use in a composable. E.G MainActivity contains a composable and I want to ass in an implementation of DestinationsNavigator to it

Amazing

How would this work with firebase-dynamic links and dynamic routing?

What you have conditional navigation i.e. if logged in home is profile if not login is home

Thanks for sharing this amazing library! Btw, can you make a video about how to handle specific top bars for two or more screens? I'm working in something like these, but i was confusing about having only one Scafold on the MainScreen, that handle the top bars using callbacks, and observing the current screen state. Or the best way is to have a Scafold on every Screen? Example: 1. First screen top bar has a search icon, that can filter something. 2. Second screen has a back button, search icon disappears. 3. Third Screen has a menu button, back button disappears. Maybe this library can already help with that... Another thing, is how to implement a Scrollbar on a LazyColumn.

one beginner question still is open to me: How can i pass a viewmodel to share it with all composables in this navgraph. passing it as parameter doesn't work

I love your native android videos and i really enjoy them , But i was wondering how powerfull kotlin and compose can be so, Can you make a compose app, that tracks (or prevents a phone from being flashed if it is stolen,lost e.t.c)

How do you pass parameter to the starting composable?

I'm not really a fan of using 3rd party, unofficial libraries in my projects... especially libraries that have their roots so deep into the system. I don't want to find myself in perhaps 5 years or more having to rip apart the whole app because i cannot compile it anymore since an unofficial 3rd party library is being deprecated or doesn't behave correctly with future versions of Android or the official libraries that i already use. This of course has nothing to do with this specific library, but in general. The less you rely on 3rd party libraries, the less bad surprises you are going to have in the future. I really don't want to find myself rethinking and rewriting the navigation of an app i wrote years ago only because i did a bad choice... it is already hard enough to have to work with something YOU wrote years and years ago without even remembering what it was about, how it worked, etc. because your user asked for a new feature in an existing app you build... i don't really want to make this process even more difficult by "betting" that the libraries i used will still exist in a few years from now. So, even if it is painful, I'll stick with the official navigation recommendations from Google and wait for them to come up with an official (and fully supported) solution... and i'm already pissed by the fact that they keep changing how to develop androids apps apparently every few months forcing me to re-learn how to do things i thought were settled over and over again...

What parameter should I use for a screen preview since I have to specify a navigator as argument?

NavGraphs not found (app builded). But app bulded and I see generated class UPD: Downgrade gradle plugin to 7.3.0 do the trick. (AS use 8.0.0-alpha for new projects by default)

Is there any performance issue?

Can anyone tell me while using this library is it possible to pass data back to previous screen when navigating back? If yes how?

Gr8

I cannot make it work in a multi module project

Hey :D This is not about this Topic. More an Video Request. Can you maby do an Tutorial for an Language switcher in the App for all Text Elements. That would be so awsome :D And a Question about this Library. Is it possible that Google will Implement this in Compose themself?

Great video! can you make a follow up video with deeplinks using this library ?

The library looks simple enough to use, however, I was having some issues combing KSP (for the library) and KAPT (for Dagger Hilt - no KSP support yet) in my project. Just couldn't seem to get the two to play nice together. Order of the plugins made no difference. Otherwise, the library seems to be what we need until the Compose navigation evolves (even if it's just parcelables).

It's so cool. I like simple things because i'm stupid when programming. Brain go DUUUUUUHHHHHHHH

How to use it with BottomNavigation? How to read currentBackStackEntryAsState()

SOrry to say that but the liberary seems to be not working at all, I belive they changed it a lot without adding new dopcumentation or its stop working anyway

updated version need

Please share your theme

Thanks for your video. But I got an issue with ProfileScreenDestination. It's does have user params

Just now tried unsuccessfully to add navigation with this library. It looks like a load of crap. The documentation doesn't work. Samples from github won't run because of wrong configurations. Half of the features are already "deprecated". Wasted 3 hours of my time.

🏅

03:32 the start ist very interesting

Isn't Google going to fix compose navigation?

Crispy bacon mmmmmm....

Library looks cool but, I am not sure if passing a whole parcelable object is the best way. I think what we should do is to pass only userId and then on the next screen use a room database to get user by this specific id. What do you think? :D

Actually I didn't like it, yes it's a great work, BUT there is no way to summarize or to see the overview navGraph, no way to specify the routes, any destination can accessed any other destination, in projects with +5 screens it will very hard to maintain that if you passed your navigator everywhere

if the parcelable featture isn't provide for the compose navigation library is because is a bad practice. Id's are your friends :)

@Destination(start = true) is deprecated instead use @RootNavGraph(start = true) together with @Destination

Super Cool and Super Easy