Full Guide to Nested Navigation Graphs in Jetpack Compose

In this video you'll learn everything you need about nested navigation graphs in Jetpack Compose.

⭐ Get certificates for your future job
⭐ Save countless hours of time
⭐ 100% money back guarantee for 30 days
⭐ Become a professional Android developer now:

Get my FREE PDF about 20 things you should never do in Jetpack Compose:

💻 Let me be your mentor and become an industry-ready Android developer in 10 weeks:

Subscribe to my FREE newsletter for regular Android, Kotlin & Architecture advice!

Join this channel to get access to perks:

Get the source code for this video here:

Join my Discord server:

You like my free content? Here you can buy me a coffee:

[qqkqhce]

Thank you for this video. Sharing the view model between the screens in the nested graph was EXACTLY what I was trying to figure out.

[raghavaggarwal]

Hi Philipp, though I understood the whole video and it's context but I just think it would have been a little better if you could have added some pictorial demonstration of the navigation which you are taking as an example. Great content as usual!

[fredericoamigo]

Hey man! Thank you so much for making these brilliant hands on tutorial vids for Jetpack Compose. They are really high quality and help me out a lot.

Keep up the good work! You are truly one of the best code-YouTubers out there!

[ahmrh]

i searched everywhere for this and your videos always helped me, thank you!

[RichardMaidenCG]

The solution I was looking for, thanks a lot, Philipp! I love your videos

[n]

Damn I finally understand, thank you. I couldn’t figure out how to move from one screen to another. Each time, for some reason, I got the controller out again through the remember. Now it’s clear, thank you again

[ericwathome]

I was really thinking of implemetning this in a project I'm working on. Thanks for this man

[Narazgul]

Wie gewohnt toller Content der mir direkt wieder weiter hilft! Noch ein kleiner Verbesserungsvorschlag: Eine Grafik, die den gesamten Prozess schematisch darstellt kann hier wohlmöglich noch für weitere Klarheit sorgen. Ich persönlich würde vermutlich auch jedem Nested Graph seine eigene file geben, da es in größeren Programmen für mich schnell unübersichtlich wird. Dann kann man schon in der Ordnerstruktur ablesen, welche Graphs es gibt. Wohlmöglich korrelieren die dann sogar mit Feature Modulen und helfen bei der Übersicht über das Projekt ✌

[stoyan_vuchev]

Just on time for another great guide! I was not aware that it is possible to pop the whole navigation graph using the graph route. I've been using the start destination route for poping the back stack the whole time. 😅

[ngomdecadetkamdaou]

Right at the best moment. Thanks, Philipp, you are amazing!

[codelabs.]

Thanks for the video. Keep up the good work!

[duongvu]

One downside to call out for this approach is that you won't be able to wrap, say, the calendar nested graph inside a Scaffold for things like tab navigation. You either have to wrap the whole NavHost inside one Scaffold and optionally show/hide the app nav bars or use a single composable() as a container for multiple tabs.

[norayrmovsisyan]

Hi Philipp. Thank you for great video. Hope we will see such a videos too long time.

[ChrisAthanas]

I fixed this example and added UI elements, the PR is available in Philitps' Repo for this video

[neerajverma]

We need more detailed video on this topic such as how to navigate between nested graphs and pass data between

[xavierrispal]

Quite interesting video !! Thanks for that. Does it mean you don't use anymore this dependency in your projects ?

[SanjarSuvonov]

Hi Philipp, please show us navigation with bottombar(bottom navigation view). It has two navGraph. Managing these is a problem. Make a video about it.

[robchr]

Thanks a lot. This saved my bacon from having to do a huge refactor!

[frankyjunior]

Please make video nested nav with compose destinations libs. Thank you

[ngapps]

I wonder how it gonna be in larger project, where you have signin/signup feature and 5 screens under Navigation Rail / Bottom Navigation.
Should it be like Main NavHost, Nested navigation graph for login, Nested navigation graph for main app, with 5 nested graphs inside?