How to use Flutter Navigator 2.0? | Warning: it's complicated 

0:35 Forking ohh.... Okay

Thanks for this simple and approachable intro to Nav2. As noticed and commented, it is a lot of boilerplate indeed. Reason for that is to enable building navigators for much more complicated cases. For basic stack push/pop and its named variant, Nav1 or packages based on it to even simplify it (eg autoroute, fluro, get) are still very good alternatives. I am looking forward to seeing packages that make using Nav2 simpler and less boilerplaty for some specific more advanced use cases, often related to Web and Desktop navigation and their seamless transition to phone sized navigation. Not only url handling, but eg inserting master/child view page as poppable page when you resize the screen to phone size. Totally doable now that you can easily control the page stack.

Bro you have a such great personality and your explanation is on the point and made the things so easy to be absorbed thanks bro

Not a fan of how most people do navigation... I tend to hide the navigation logic inside the page you are navigating to So when navigating I just call a async handler: final result = await BookPage.navigate(context,book); Then I can handle the result of the popped page in a linear fashion. I think people are overcomplicating navigation... Thanks for the video, nice introduction to the new navigator

Great video, it was clear and simply. I was able to get the main concept of the nav. Keep up the great work!!👍🏿👍🏿

I really like your method to explain and share in flutter learning (in many of your videos), put it in real life case to make me more easy to understand the logic inside of coding, great works and thanks!

What extension of vscode do you use to mark code blocks with white lines? Thanks 🙂

Tnank you very much... how do you zoom.. is it a shortcut? OR zooming is done while editing the video?

Hi, please Let me know if I add a new page support page totally unrelated to book and doesn't depend on _selected book . On a button click from anywhere take to support page . How can we navigate from any page to support page

those are some crazy boilerplate code. No thanks I'll keep using nav 1.0

I'll keep using auto_route instead :D

Very well explained Thanks

I am more interested the vs code extension you use to display the errors on the same line. What is the extension called?😁

Does it mean tha the whole application is updated every time a navigation flow is executed?

I thumb up because it is easy to follow as a basic introduction to Navigator 2.0 The best moment is when he says: "Personally, I don't know exactly what onPopPage does". 😀 That comment tells how messy is the new Navigator API.

Great video! Now, about the new navigator.... what a mess.

Hi I love your videos, one question how do you get the 'red' comments in VSCode while you are typing in commnads please, thanks Pierre

hi sir, i enjoy watching your videos. I was going to ask something.Which theme are you using?

sorry, but this approach of creating stateful widget instead of stateless just because of navigation 2.0, sucks.

Can I ask how I can set the initial route (at first launch of the app) to '/home' instead of '/'?

What vscode plugin gives you the errors inline with the code?

so basically it listens to the change of selected book automatically so we just change the state that's all that's kind of cool with state management its easy

I loved your video man it was cristal clear thanks Maybe a quick code recap would have been perfect at the end :)

Tutorial on how you made the books app it looks sick

0:35 you can follow along this tutorial by fu*king this project

Isn't the level of the audio extremely low?

Make sure you 'fokk' the project !

I thick it's so f**kable in huge project . just use 1.0 version :)

thanks for this video but i think old one is better

it really is complicated

thanks man!

i dont understand lol.. how can u navigate nnext screen

in search of gold we lost Dimond be like :p

why it so complex now? for what?

Audio is way too low!

BRILLIANT!!!

Arguably the worst thing Flutter introduced so far

what's hard about this? XD