Not sure what I will do for youtube but I will sometime in the future have a open-source repo and the course will also go more in-depth on it soon as well!

@@RobertBrunhage Awesome!! 🚀

Going to do my best haha

Yes, the best scenario will always be generating the tests with a single OS. I am for sure hoping people share some insights of potential better solutions. Mainly wanted to share my experience!

Pinning this. interesting, do you have some links? Would love to learn more here and make sure I share a better approach next time. Seen this approach in multiple large codebases as well so for sure those small differences could be valid, but they might also be so small that they haven't mattered.

@@RobertBrunhage there is the opened issue on flutter github #111739 related to M1 machines golden tests mismatch.

Would of course mean a ton if you get the course for support, but will try to add more things in the end so that even you can find some small nuggets in there! Related to navigation the main ones imo are go_router and auto_route. I am still kind of conflicted on navigation in Flutter so will see when a video comes out with that haha

Really I'm always using Stacked for every app. I love how manageable and readable my code becomes without doing or adding too much of a boilerplate.

chad

Usually streams can be a foot-gun in many scenarios but it's also a valid approach and built-in. I have nothing against it, I just think there is better approaches to 95% of the scenarios.

Exactly! I love stacked for being simple and without a lot of dependencies. Just reducing boilerplate.

It's not even advice, it's Robert's approach as the title clearly states. But mvvm is clean architecture, they are not mutually exclusive 😅 And the feature based folder structure can still be used with mvvm architecture. It's rather bold calling something bad advice while not knowing what you're talking about.

@@aymanbarghout9106 I can accept it's his opinion, but still he is sharing it, so regardless of the validity of the information, he is still sharing it. Second, mvvm is not clean architecture for flutter development. That would be as if you told me mvc (model-view-controller) is clean architecture, hello 1973, please take C back.. and honestly, saying "you don't understand" is very weak argument. He is not not even telling them to use Bloc (even though 99.9% of industry is using it), it's just not a good look when you still have this "wHaT sTaTe MaNaGeMenT yOu ShOuLd UsE".. I am telling you honestly, some kids will look at this, and try to follow this advice.. there are industry standards for a REASON, and he should at least respect that to mention that.. this is not a mainstream advice which he is giving, and beginners should know that. And to repeat again,, MVVM is NOT a clean architecture in flutter development. If you don't believe me, go speak with cloude 3.5.

fully agreed, Clean architecture kind of old and even some famous framework likr laravel didnt do it. plus MVVM cannot be compared to Clean Architecture i think. you can do both​@@aymanbarghout9106

@oijgg3p It's his opinion and definitely it can be wrong or even a bad one depending on who you ask but you can just say your counter approach and give reasons behind it, saying it's bad and calling it a day is not benefiting anyone, there is nothing set in stones. MVVM is a UI architecture pattern not the same as MVC and can be part of clean architecture, again they are not mutually exclusive, it's just how you architecture the presentation layer. I didn't say you don't understand, sorry if it came out that way, I said you don't know what you were talking about in this instance and I think the point still stands if your source of truth is AI and not experience - this is an assumption based on your last sentence -.

Simply not true. The official flutter channel has feature stacked (which is MVVM) recently. Also, you can do feature based architecture with MVVM and even clean architecture with service locators. It's quite obvious to do it if you think about it.

In my opinion you should not intertwine caching and state management. Just take react as an example: React-Query is awesome for caching, but nobody would like to have that baked into a state management solution like Redux.

I did try to cover that in the video of the potential downsides of using packages vs not. People are free to use whatever approach they want. If you prefer using bloc, blocbuilder, bloc in tests etc you are free to do so or if that is riverpod or any other package. I just personally found that the overhead of those packages end up being a net negative, rather than using the primitives already in the sdk that we have had for years (this has been true in teams as well as people end up trying to utilize the packages differently, in my experience). Teams are free to choose whatever approach they see fit to make an application. But I might also note that a lot of people end up relying on those packages so hard that they forget what they actually do, which is not hard to do yourself (or difficult) and will scale, really really well.

go with bloc and don't listen to these people they are just milking the youtube algorithm for views

​@@RobertBrunhage It will mostly take the same effort to switch from the packages, or your solution to a new solution since both are following a similar pattern. When it comes to updating the packages it still didn't make sense to me because I'm not forced to update and I'll mostly do it only when I can afford to and updating is a good idea in general so I can get the improvements and new features. And when it comes to small projects, it's also a great idea to use them from the start so that I can scale the project better later.

Hard agree. The lack of recommendations are nice in some aspects and in other aspects, not so much

You are free to use whatever you want. I just found personally that it's usually a higher burden on the codebase than it needs to be.

@@RobertBrunhage I am intrigued. I should give it a try in a typical to-do-app.

Sweet, maybe I shouldn't take a 1 year break again haha

@@RobertBrunhage Well, you could, but I would prefer some new content too.