I agree, but my argument was if that was a big reason for 2.0 being so confusing, and if possible to make 2.0 simple to use for everybody, then maybe deprecate it
Nope, but I also haven't looked for it much. I do know the Flutter team is aware of this, and im pretty sure is working on making it easier to use somehow
Navigator 2 seems to be focused on web. In mobile its common to open same screens stacked on top of each other. For example in instagram, you tap a profile, tap a photo, tap on others profile from comments, and so forth. This means, I need to keep track of page history which fits better with imperitive. I found myself implementing Nav 1.0 (push and pop) for Nav 2.0 I just need android back button to be handled on the nested navigator but it only works on Nav 2.0 theres no way around it.
How do you think nav 2.0 compares to the nav capabilities of the GetX package? I've been using this for a while now (not just for routing, but for state mgmt also) and I think it's very easy to use.
Personally I haven't used GetX for a while. I actually haven't done that much development except for one project the past couple months. My thought about GetX is it makes things very simple. Which is great if you are starting out. It works well and I don't see much wrong with it. But personally I have been using Riverpod, because it has some nice safety features as well as other things. Nav 2.0 allows you to control the whole stack, I don't believe GetX lets you do that. Again, those are specific things that are probably not necessary to have a complete app. My thoughts are GetX is fine, and if it does the job for you, no need to change anything. But personal preference is Riverpod. And I don't really have a preference for navigation yet. I haven't looked into many solutions, but I think auto_route package looks to be a good one
The complexity is in understanding but not in the navigator itself. With the help of package like go_router, it's far more easy and quite understandable and also explains the system flow through router and in long run I myself feel like it keeps the flow of app structured with the help of properly defined routes.
Whatever works for you is the best 😊. I think the "best" is Nav 2.0 since it gives you so much control, but it might be too hard to use, so I don't even know haha
Totally agree with you! Nav 1.0 is good and simple, but if they want to bring a change for the best, it should've been like an update, not a whole backward compatible remake, in my opinion that is.
I actually prefer the imperative way for Navigation. You execute and you're done like with html href. More boilerplate for multiple page management is understandable but not for core web support. I'm not sure if forward and back seemed to work in the browser on the dev channel with navigator 1.0 today though. Can anyone confirm?
I am pretty sure forward and backward never worked with imperative option, and was part of the reason they decided to make a 2.0. But yea you have some valid arguments.
Hey, great video, I have understood most of the context, my english listening is not the best. I have been having a problem with Navigator 2.0, specially with native navigation, for example, when I press the back button in Android the app is closed.
I very much agree with this explanation about Navition 2.0. I still prefer GetX for Navigation and State Management among other very cool features. Thank for share with us your opinion.
hey Tadas, you should rank state management packages and navigation packages and make it as a revisited video. OMG i finished looking the video, this is too much of a sipderweb, lol. it seems very powerfull and granular but the boilerplate code is a bit much.
Oh man I can just imagine the backlash of making a ranked state management video 😂. But I am thinking about it. It would definitely be more of an opinion video, since they’re all good solutions. And really comes down to personal preference
Deprecating 1.0 is not a really good idea this is what I feel🤔 There was only one time when I felt of using navigator 2.0 for my mobile app. Hoping that there will be some better tutorial or better way of implementing it.
I agree at this point it would not be a good idea to depreciate it. BUT if 2.0 was easy to use and simple to understand, I think it would make a lot of things easier, and 1.0 would not be necessary
This is not something new! They promised full web support for 2020 but things didn't go well(the only major feature was a very bad implementation of nullable types), so they are bringing new features without the necessary abstraction layer that makes them user-friendly and wait for the community to help. This is not the first time! They did the same with other core features like inherited widget and let the community provide the syntactic sugar(provider etc). This is the open-source era... where is no reason to hire programmers when you can transform the whole community into free employees (Microsoft did the same with C#).
I think for mobile apps, 1.0 is sufficient. But even then, I feel like there is a reason why they made a 2.0. To solve problems. Would of just been nice if it was a bit simpler.
Google is the reason why I appreciate Apple for their way of doing things Most times you don't even need documentation to understand some of Apple's frameworks
Same goes for me, but in reverse. - took me 3 months to be able to join Apple developer because of Apple's shitty payment system; - rejections reasons are extremely vague and sometimes outright retarded; - Testflight sucks big time; - a responsive splash screen is harder to implement on IOS; The list can go on.
ur title lol.. should change it.. best explain about navigator 2.0 .. but ur clickbait is backward.. actually I dont want click this kind of clickbait.. but the video itself is good and understand than other video
@@tadaspetra I dont know, "Navigator 2.0 is complicated than you think" something like that, if someone make clickbait "'is bad or suck" it like drama to me.. no information at all.. but your video different
I totally agree,
I feel that I was writing the package myself rather than using something
that is supposed to be built in
Yes that is exactly my feeling
If they deprecate Navigator 1.0, we're all doomed.
throw DeveloperException();
I agree, but my argument was if that was a big reason for 2.0 being so confusing, and if possible to make 2.0 simple to use for everybody, then maybe deprecate it
Nothing a little rewrite won't fix.
@@tadaspetra How about making a package which uses navigator 2.0 under the hood? Which gives a more simpler API
@@blank-vw2sb there are some packages out there for it. I mentioned them later in the video. My favorite one right now is auto_route I think
Hi Tadas. Did you find any good remedies for this problem 6 months later...?
Nope, but I also haven't looked for it much. I do know the Flutter team is aware of this, and im pretty sure is working on making it easier to use somehow
@@tadaspetra So, are there any updates 8 months after this video :D
@@furkanvatandas4819 Nope. I know the packages are getting some praise though, so worth a look
Navigator 2 seems to be focused on web. In mobile its common to open same screens stacked on top of each other. For example in instagram, you tap a profile, tap a photo, tap on others profile from comments, and so forth. This means, I need to keep track of page history which fits better with imperitive. I found myself implementing Nav 1.0 (push and pop) for Nav 2.0
I just need android back button to be handled on the nested navigator but it only works on Nav 2.0 theres no way around it.
How do you think nav 2.0 compares to the nav capabilities of the GetX package? I've been using this for a while now (not just for routing, but for state mgmt also) and I think it's very easy to use.
Personally I haven't used GetX for a while. I actually haven't done that much development except for one project the past couple months.
My thought about GetX is it makes things very simple. Which is great if you are starting out. It works well and I don't see much wrong with it. But personally I have been using Riverpod, because it has some nice safety features as well as other things. Nav 2.0 allows you to control the whole stack, I don't believe GetX lets you do that.
Again, those are specific things that are probably not necessary to have a complete app. My thoughts are GetX is fine, and if it does the job for you, no need to change anything. But personal preference is Riverpod. And I don't really have a preference for navigation yet. I haven't looked into many solutions, but I think auto_route package looks to be a good one
The complexity is in understanding but not in the navigator itself. With the help of package like go_router, it's far more easy and quite understandable and also explains the system flow through router and in long run I myself feel like it keeps the flow of app structured with the help of properly defined routes.
I've heard good things about go_router
At 6:20, that's not a backslash. Just a slash. Backslash is like \, slash is /.
I will have to redo the video now because of this 🙃
Same thing I thought, why do I need a package to fulfill a basic need like navigation. Still freaks me out
I use GetX for route management. By the way, which is best you think?
Whatever works for you is the best 😊. I think the "best" is Nav 2.0 since it gives you so much control, but it might be too hard to use, so I don't even know haha
Totally agree, 2.0 needs too much setting up before letting the dev use it, it also too prone to implementation errors
Great video Tadas!
Thanks Danny 😊
Totally agree with you! Nav 1.0 is good and simple, but if they want to bring a change for the best, it should've been like an update, not a whole backward compatible remake, in my opinion that is.
Hi Tadas, I wish you happy New year. What do you think about make tutorial of two packages(dio, freezed). I like your videos and have a nice day.
I will look into it 😊
Finally got a Navigator 2.0 video from you😅😂
I actually prefer the imperative way for Navigation. You execute and you're done like with html href. More boilerplate for multiple page management is understandable but not for core web support. I'm not sure if forward and back seemed to work in the browser on the dev channel with navigator 1.0 today though. Can anyone confirm?
I am pretty sure forward and backward never worked with imperative option, and was part of the reason they decided to make a 2.0. But yea you have some valid arguments.
Šaunuolis! Geri video :)
Aciu :)
Hey, great video, I have understood most of the context, my english listening is not the best. I have been having a problem with Navigator 2.0, specially with native navigation, for example, when I press the back button in Android the app is closed.
You might be popping all pages so now it's only one page so aap get closed
I very much agree with this explanation about Navition 2.0. I still prefer GetX for Navigation and State Management among other very cool features. Thank for share with us your opinion.
I’m happy most people agree with me. I was worried I’d miss a major flaw in my arguments and would looks dumb 😂
God don't use GetX
Many beginner flutter developers are facing problem with responsiveness for all devices. Can you please make a tutorial Tadas? 🙏🏼
I made one a long time ago, it’s in the flutter basics playlist. But I’ll look into making an updated one
@@tadaspetra That would be very helpful Tadas.
hey Tadas, you should rank state management packages and navigation packages and make it as a revisited video. OMG i finished looking the video, this is too much of a sipderweb, lol. it seems very powerfull and granular but the boilerplate code is a bit much.
Oh man I can just imagine the backlash of making a ranked state management video 😂. But I am thinking about it. It would definitely be more of an opinion video, since they’re all good solutions. And really comes down to personal preference
@@tadaspetra yes you have to be carefull, jjust put "MY" in your vid so thats enough for viewers to know that is your opinion
Deprecating 1.0 is not a really good idea this is what I feel🤔
There was only one time when I felt of using navigator 2.0 for my mobile app.
Hoping that there will be some better tutorial or better way of implementing it.
I agree at this point it would not be a good idea to depreciate it. BUT if 2.0 was easy to use and simple to understand, I think it would make a lot of things easier, and 1.0 would not be necessary
@@tadaspetra yes deprecate it only if they make it easy...
GetX seems to be much more strait forward....
replaces too much, from what I've seen. I can rip and replace the router, but not Provider. Need to do more research.
This is not something new! They promised full web support for 2020 but things didn't go well(the only major feature was a very bad implementation of nullable types), so they are bringing new features without the necessary abstraction layer that makes them user-friendly and wait for the community to help. This is not the first time! They did the same with other core features like inherited widget and let the community provide the syntactic sugar(provider etc). This is the open-source era... where is no reason to hire programmers when you can transform the whole community into free employees (Microsoft did the same with C#).
Yea you are right. But I guess I just wish it was different 😕
Yea you are right. But I guess I just wish it was different 😕
I have read and seen many example about Navigator 2.0 and it was too confusing I thought they just made it for web. "yes I know, I am stupid"
I think for mobile apps, 1.0 is sufficient. But even then, I feel like there is a reason why they made a 2.0. To solve problems. Would of just been nice if it was a bit simpler.
I use flutter_modular for route management
You saved me
Thank u so muchhhh😭
Great 👌
Can you make video how to build chat app using firebase
I am follow you from Egypt 🌷
I will look into it. Thank you for following along :)
Agree 👍
Google is the reason why I appreciate Apple for their way of doing things
Most times you don't even need documentation to understand some of Apple's frameworks
I've never worked with Apple's frameworks, I should give it a try
Except CoreData? 🤪
Same goes for me, but in reverse.
- took me 3 months to be able to join Apple developer because of Apple's shitty payment system;
- rejections reasons are extremely vague and sometimes outright retarded;
- Testflight sucks big time;
- a responsive splash screen is harder to implement on IOS;
The list can go on.
Wtf is this Navigator 2.0! So much boilerplate
All you need is GetX, and do not be sprayed with other packages
Ugh!
ur title lol.. should change it.. best explain about navigator 2.0 .. but ur clickbait is backward.. actually I dont want click this kind of clickbait.. but the video itself is good and understand than other video
Appreciate the feedback. Any suggestions?
@@tadaspetra I dont know, "Navigator 2.0 is complicated than you think" something like that, if someone make clickbait "'is bad or suck" it like drama to me.. no information at all.. but your video different
Very nice 😍💋 💝💖♥️❤️
What happened to you ?
@@thehumbleservant21 😂😂😂😂🤣🤣🤣🤣🤣