Meet Voyager: A Kotlin Compose Multiplatform Navigation Solution

[@dinarastepina8707]

I loved it! As someone who’s always in search of the best navigation solution, currently using Voyager and it’s the best one I’ve tried so far

[@emmanuelmtera5936]

So simple to use

[@free_guy00]

Amazing...Please follow up with the Multi Module Navigation using Voyager

[@yanneckreiss]

I will put it on my video idea list 🙂

[@MathanMaheswaran]

Hey Yanneck, thanks for your amazing videos about Compose Multiplatform 🙏🏾. Currenty I start to learn building apps with compose. Will you bring more videos in the future?

[@yanneckreiss]

Thank you for watching. I am glad you like them 😊 Yes I will, I already have some new video ideas but I am working full time as a software developer and therefore don't have that much time to release that often 😅

[@MathanMaheswaran]

@@yanneckreiss I can understand 😅. Thanks anyway 🙏🏾

[@harshagarwal6750]

Super Helpful!!!

[@MRonak]

Hello, nice tutorial! Was wondering if there is a way to change the navigation transition for a certain screen navigation or do i have to use the initially set transition across the app?

[@ohiorenuaaigboje7500]

This is so amazing and simple

[@sijanneupane]

Helped alot! thanks! keep making more!

[@scotty3024]

You are amazing! Thank you so much for the tutorial!

[@yanneckreiss]

Thank you for watching 😊

[@yunusemrehalil1036]

Great video. Thanks bro.

[@georgeopiyo6004]

Is it possible to share the same view model between two screens and how do you get the same instance (spolier alert still new to this). Use case I have some data in screen a that is a large data set and I dont want to pass it as an argument . Is this correct ?

[@eduardoruesta5180]

Love it!!! thanks! im working on a sample app using Compose Multiplatform. the only doubt i have is that the back navigation is not working on my iOS simulator... How can i go back?

[@trevordick2695]

This video was amazing thank you so much!

[@BasantKumar-bg3fg]

Just Wow, amazing, its helped me a lot

[@yanneckreiss]

Thank you very much 😊 I am happy my video was helpful for you

[@riyupapa39]

Good video. I have a question. compose-navigation library have a problem. That is when a conposable has WebView and navigate to another conposable and popbackstack, the WebView is disposed and recreated. How about Voyager?

[@goalabs]

please cover more videos on using this with the kotlin jvm desktop app..

[@yanneckreiss]

Thanks for your comment 🙂 I am definitely planning to make videos about how to develop not only for mobile but also for web and desktop with compose multiplatform as well in the future

[@galaxiegalaxie5003]

Very CoOL LibrarY WoW😊❤

[@kadwa_sachx]

I choosed the decompose that seperates the ui logic from buissness logic.

[@aditya3n]

Let say i have 2 tabs, Home and Profile. When I'm on Profile screen and press back btn, the expectation is to be redirected back to Home. But currently the output is it's closing the app, instead of navigating to previous screen. Any solution for this?

[@sandeepmishra7971]

Hey, I am using one viewModel inside my Screen1 class and sharing that to Screen2 class But when i am using navigator.push(Screen2(viewModel)) I am not able to get data from my viewModel's state class data but if i use Screen2(viewModel) instead i am getting viewModel's state class data Is there anything i am missing while using Voyager with viewModel?

[@CyberSoftSolution]

But How to handle BackStack in TabNavigation then ?

[@YassineMikeAlpha]

The content is amazing. Keep it up.

[@yanneckreiss]

Thank you 😊

[@RachelNayfill]

Hey have tried using deep links and voyager

[@valhallagaming4022]

Hi...i am just starting Android development using kotlin......so should I start with native Android development only or should i Start with kotlin multi platform can u guide me with this

[@yanneckreiss]

It depends on what you are trying to achieve and your current knowledge in programming in general. If you already started with learning native Android development, I'd suggest to first get some practice with it and maybe create an example app for yourself (or even release it 😉). In my opinion that is the best way to learn a new programming language or framework. Then expand your knowledge to a broader field like for example KMP Hope that helps 🙂

[@anasfarhad2845]

How about if someone wants to send back args from Screen B to Screen A?

[@_hudeifa23]

what if i want some screens not to have bottombar ??

[@NoPainInLife]

Voyager is not working for Web. Any ideas ?

[@hudeifagithub]

is compose multiplatform good for medium apps in 2024 ?

[@niloythings]

How do I pass a data model class or pojo class from one screen to another screen?

[@yanneckreiss]

The argument just needs to implement Serializable. You can check out the official Voyager documentation for further information :)

[@andy_lamax]

now, lets do deep linking with it

[@RachelNayfill]

Hey. Have you tried it? I'd love to see the implementation

[@MichaKrasowski]

@@RachelNayfill There is none. You need to integrate with 3rd party like Rinku lib

[@renzocontreras123]

Navigation Drawer?

[@jyashi1]

Messaging here to find out my handle name

[@jyashi1]

Ahhh its @jyashi1

[@yanneckreiss]

Haha I am glad you were able to find it out 😄

[@MichaKrasowski]

Easy nor documented way to pass navigation arguments to the ScreenModel? Nope. Deeplinking? Non-existent. Toy library.

[@BasantKumar-bg3fg]

it's working good but there are an issue when i am navigating to another screen with arguments and whenever apps is going to background it's getting crash in android, it's throwing IOException ("java.lang.RuntimeException: Parcelable encountered IOException writing serializable object (name = LoginScreen)")

[@dxvfdfx]

it' really weird why jetbrains even don't provide a basic navigation solution

[@yanneckreiss]

I think they are still working on it and will provide one in the future (at least they state so in the link I provided in the video description). Until then we can make use of Voyager or alternative solutions. Again, thank you for watching 😊

[@justinsmith3981]

"Navigation is a key part of modern UI applications that allows users to navigate between different application screens. Unfortunately, the Navigation component from Jetpack Compose's suite of libraries is currently unavailable in Compose Multiplatform. However, there are other third-party alternatives that you can choose from:" - JetBrains

[@dleonardo3238]

Jetpack compose's navigation sucks anyway😂