Shared Navigation on Kotlin Multiplatform with Decompose (KMP)

In this video, you'll learn how you can implement shared navigation with the Decompose library for your Kotlin Multiplatform project. (iOS + Android)

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

⭐ Courses with real-life practices
⭐ Save countless hours of time
⭐ 100% money back guarantee for 30 days
⭐ Become a professional Android developer now:

🎁 Get my FREE 4.5h course "The Best Practice Guide to Android Architecture":

Read our weekly Android blog:

Join my Discord server:

Compose MP Project Wizard:

Decompose Docs:

Get the source code for this video on GitHub:

[treasuretechnology]

Decompose is one of the best multi platform navigation library out there. good stuff Philipp

[rakam.a]

Can you do tutorial how to modularize Compose Multiplatform projects?

[mahmoudalkateb]

YES FINALLY a comprehensive video about this topic!

[Prod-]

Appreciate the video.

Coming from a Xamarin background this seems like a staggering amount of code for navigating between two screens.

[TheZukkino]

Really interesting. I'd like to undestand how to manage all this stuff with different build variants, each one with a different navigation app tree.
Thanks Philipp for your video. The content is always super clear.

[MobileMastersAndroidiOS]

Your videos are the best on the topic of Kotlin Multiplatform Projects!

[thomaswaldorf]

33:05 Xcode usually makes me select my Team from Signing & Capabilities, and the Xcode Simulator makes me sign into my developer account before an initial run. :)

[roshkaalex]

Thank you! We are waighig for more kmm videos ! For examle backgroung services (also workmanagers and backgroung tasks and etc). Location managers, Stomp client and etc

[cbnewham_ai]

I'd like to see you do a video on PreCompose which is much more along the lines of the Jetpack navigation. This Decompose library is way too over-engineered, like something Google would write (but hey, they got Jetpack navigation right! ). Nobody needs this complexity in an app - certainly not smaller apps.

[akardas]

please make a video for Voyager library also

[abada-s]

This is a great straightforward I like it, I hope to see something like compose destinations in the future 😊

[thomaswaldorf]

17:05 while using Fleet, I had to manually declare import :)

[livionaef]

Hi Philipp is there an easy way to use different product flavors with the Kotlin Multiplatform approach? 🤔

[dleonardo]

would you prefer decompose over the default navigation also for non kmp projects?

[arctan-k]

I used this library last year when I worked on KMP project

[DjuroRadusinovic]

At @31:50 you don't need to pass text field explicitly, just take it from the component :D

[vladalexeev]

So you pass viewModel to Composable screen istead of a ViewState and pass lambdas to navigation straight from Navigation controller? I want to pass only ViewState to my Screen, how do I do it with this decompose?

[deepaksingh-qdxm]

why everything in android a overcomplicated thing

[iZakirSheikh]

Hay Philip. Thanks for your tutorials.
One request. Would you please provide a tutorial about how to publish app to fDroid. Thanks

[ishubhamsingh]

For now voyager seems to be the simplest navigation library for compose multi-platform. Decompose is good but it just requires too much setup and boilerplate code for even simplest navigation, doesn't make sense to spend so much time on setting up navigation specially in smaller apps.