Flutter Sailor Navigation Tutorial - The Simplest Navigator Library? 

Thank you for doing a tutorial on my library. Appreciate it man! 🙂 I will see what can be done to make params more type safe. Also more features are coming soon 😉

16:53 "Let's now move to arguments, which are in my opinion the much*&*&$#&#&$#&$#*$&#*$" Holy sh*t! that jump scared me!

You are one of the Best Flutter Content creators out there. Between Division and Sailor, I don't want to use any default styling or navigation on my projects, hehe.

Nice one! I'm looking for some better navigation libraries. Will definitely see how this feels in a large code base. Keep it up.

great tutorials, mat. please keep them coming.

Awesome stuff as usual!

Nice video, thanks! I was not aware of this Navigation package, seems to be fairly new and already very capable. As an idea for future tutorial and follow-up to your navigation tutorials: When navigation packages for Flutter grow in quantity (which I assume they will), it might be helpful to have some kind of comparison of them, eg Flutter standard named routes vs Fluro vs Sailor vs "NNN". Where one could compare pros/cons of each one and give recommendations on when you might want to use a certain package or just stick to Flutter standard navigation, which after all is fairly extensive and capable as well. Getting rid of the context from navigation could be useful sometimes. I've tried Fluro, it is OK as well, Sailor looks fresh and very interesting too, certainly easy to make a route observer and custom animations with it, the mixin for the args is neat too. Most of the time I find that using standard named routes in Flutter and setting up generateRoute function with named routes and defining consts for the route names of course, is enough. You can also setup static const id:s for your routes in each Widget with a route. Not really needed, but it just makes it super easy to remember them, especially if all your routes use the same principle, e.g. like "static const ScreenOne.id = kScreenOne;" where the static class const refers to the const string name in question. Which you can then setup for all routes in one const file for easy updates. When you have over 100 of them it helps if they are in one place. You can of course do class based arguments with Flutter standard named routes as well fairly easily, like I do believe you show in another tutorial as well. Changing transitions is totally doable too, but a bit tedious. I made a concept setup where Android and iOS by default use their platform page transitions, but web/desktop uses no transitions by default,, Users can then in the App settings change it so that e.g. iOS standard page transitions are used on Android or Web/Desktop platform instead, if they for some reason want to do that. :) It was actually easier to do than I thought it would be, but that was mostly because I could hook it into a very extensive in app custom theme builder that I had already implemented.

Attending the websummit in lisbon this week but will check it out afterwards for sure 🤘 keep up the amazon work 🔥😊

Great!

Hi thanks for this library which makes the code much more readable:) Does working with Hero's have any advantages/disadvantages using Sailor?

Almost got a heart attack at 16:53

Nice plugin Reso. NodeJSish style. But I think it's a bit over coding. Not if you need that fancy extra features. Especially the last animation LOL. thank you for great work! cheers

sailor lossing passed params on reload, any way to persist params?

Where is the link

I think you should re-upload this video, content is really good and easily understandable but at 16:53 there's some noise, and it scared the shit out of me. The reason it should be re-uploaded is that many cardio patients might be watching this video.

What is the difference between fluro and sailor ?

ah yes, this route mechanism looks promising.

I almost farted at 16:54