Flutter TDD Clean Architecture Course [1] - Explanation & Project Structure 

Man, claps to you. Top quality and for free. Thanks for all this content. Really appreciated.

This is an amazing course you've put together, really appreciate all the hard work you put into it. In the future would love to hear more about how to handle more complex cases with full CRUD operations, as well as multiple views/blocs/repositories which are interdependent. Looking forward to the next class!

After watching ton of videos...I finally found yours who took time to go into the depth of things. Thank you

Matej, thank you so much for existing. You aim to provide the best app development courses/tutorials out there and in all of the research I have done over the years, yours have always prove to be a major cut above the rest-your pacing, your choice of words, your easy-going vocal demeanor-it's untouchable. I cannot express how truly thankful I am for you and the wonderful work you do for the entire developer community. Keep doing what you do best. Much love and support, brother. 💙

Thank you for the tutorial! Finally a real world implementation of a clean architecture instead just the common tutorials on how to create this and that. Your explanation is very clear and easy to understand.

Best video I've ever seen about flutter architecture! Thank you very much for the content!

Perfect explanations, perfect speed. Fantastic job. Best Flutter Tutorial I've seen on RU-vid! Hats Off to you Sir!

What an amazing series. I'm so thankful for all of the efforts you put into this series. Keep it up

I'm comming from mvvm pattern and I was looking for something like that for flutter really long time and I finaly found. Thanks a lot, amazing video!!

I'm in the middle of my first flutter project, And I wish I had found you earlier. I'm a fan of Uncle Bob and clean architecture.

This is what I need. Love it, big thanks, excellent work dude!

The first person who explained why you have to have both models and entities, great stuff!

Thank you from Syria, This is literally the corner stone I was looking for.

Nice one. A lot of tutorials are focused on explaing one thing, a couple of them are showing archtectirure patterns, almost none of them are explaing testing. You are planning to create it all together and whats more with TDD. Awsome job and desire to share knowledge. Thanks for that and I hope, We’ll see a lot of videos from you

OH MY GOD! You make me to understand a lot design, framework , code I have coding 2 year . You're video open my mind forever. Thanks , sir.

Well explained in a simple and understandable way, now I understand flutter as pro

ex iOS now Flutter dev here. just found out about this content and amazed by it! Keep up the great work.

What a good video, it brings a lot to good practices for development with flutter. Greetings from Peru!!

Thanks for this great video! Coding is easy, but designing a good architecture is quite a challenge.

Amazing stuff, as usual. You're literally the best Flutter RU-vidr out there. Keep up the good work!

your illustration is extremely clear and simple

really amazing to see this advanced stuff

VERY good explanation. Thanks a lot for sharing this with us!

Cool guy, looking forward to seeing the next lesson.

Firstly: Thankyou @ResoCoder for your overwhelming tutorials, You're Awesome!! Secondly: For All of you looking for same icons add this in your setting.json file: "material-icon-theme.folders.associations": { "global_state": "global", "ui": "layout", "bloc": "controller", "features":"other", "presentation":"layout", "data":"database", "domain":"rules", }, That's all folks!

its amazing and usuful thanks.Keep up the good work!

VERY HELPFUL!! Thank you 🙌🏼

This is cool stuff. Keep it up. I am learning something good here. Cheers

You are doing a great work man keep going 😀

What would I do without this video? Thanks a lot!!

Good job. Keep up the good work!!

This is great! Thank you!

Really really nice work! Thanks so much.

The file structures are really awesome and it helps me as a beginner developer, Thanks for the video

Thank you so much! This was super clear.

Thought I would add a comment here for those wondering how the entire course is instead of waiting till you are half way through and finding some modules aren't as good or lacking etc.. I can tell you, as a developer or a beginner, this course is a must because it follows solid engineering practices not ad hoc development like some other tutorials. As an experienced developer I still learned a lot and know you will as well. Thanks again RESO CODER!!!

Thank you so mucho for this amazing video!

Outstanding explanation!

thanks, it actually let me through so i could download it.

thanks a lot bro, this videos are awesome

Amazing, thank you!

Still working as of today! Thank you!

amzzing stuff sir, keep the good work up.

Love your tuts, Please make video about Best Practice in Flutter and Performance, and How to make an app Responsive in a best way. I am searching for these videos for a long time.

Thanks for the explanation.

I applied for a development job and went through 3 interviews. After the 3rd interview, I was given a take-home assignment that requires us to know clean architecture. I know nothing about clean architecture but have experience developing apps. The company gave me some slides to learn clean architecture but I don't think they explain it that well. I am reading your written tutorials and then watching the videos and taking notes. You are saving me! Thank you!

Hi, first of all, thank you for the amazing content that you provide. Since I'm talking about provide, I'd like to know if you could make a video explaining the main differences about provide and bloc, or at least point me to a direction where I can understand when would be better use one than the other. Thank you very much. I'll be watching your amazing videos.

You are awesome. Thank you for all this knowledge. (Y)

Thanks, tuto is very clean

I was just thinking to get the uncle Bob's clean architecture book and you mentioned him :D

Hey Reso ! Amazing content I think you should make a video explaining the sequence of videos a person should watch that you have uploaded to be a good flutter developer

Great. There's an "flutter modular" that is very similar, if not the same approach. The difference is that they call it modules and not features. Also, has it has a package the are some routing and DI included along side with the pattern. I will watch the playlist, this kind of stuff is really good when the app start to grow. Thanks

Thanks a lot , nice explanation

Very nice video; waiting for the next one ;) If you have shared widgets across multiples features, would you prefer to put them somewhere in core or create a shared folder in feature? I would put them in a shared folder as my widgets might have the need for state management or access data Small edit: in your written blog post you don't speak about core folder at all.

such a elaborate explanation video

The best content about Flutter. Most of content out there focus on spaghetti UI. They do not care that much about clean or even a well defined and scalable architecture.

Thank you, soo much , I was searching everywhere to learn something useful for flutter. I studied the flutter.dev documentation but still I was not able to figure out how to map my study project and also i am unemployed I hope studying your tutorials help me getting a job. You are doing great !!! :-)

Great video!!!

Nice explanation

Thank you. Its great

Perfect!

What an amazing content

Nice video thank you 🙏🏼

Interested for the next part to see how the design holds up in a larger more complex app. I’ve seen really similar designs in a web service, but I’m worried that doing things like showing data from a cached source before responding with the updated data from an api will be difficult because the repo is separated from the bloc and the domain has to pass the update through.

I just started view this tutorial i know it's old but trust me this stuff are amazing, the only down side in my opinion is the use of bloc i wanted it to be riverpod but anyways i could just adapt to riverpod thanks man you got my sub for this thanks

Amazing bro thanks

feeling excited to learn such architecture pattern. Thank you so much, sir!

The waiting is gonna be hard now... a bit like Christmas: I am going to count how often I have to sleep until it is here! Except it is harder, because I don't know the date, when your next video will be published... Awesome!

amazing ❤

Nice video!

Thanks a lot!

Thanks for the vid

Thank you so much

Gracias, muy interesante.

What an amazing series. I would to know what's the theme are you using in vsCode ?

you the master

I'd like to see how it will be wonderful with the current architecture having applied "streaming architecture" for the structure of directories.

Done!!!

You made 24 minutes video and I studied it for 3 hours :D

For each table in my database do I have to create the 3 layers? data, domain and presentation? in the case of working with an api rest, already knowing your model

Thank you :-)

Hi. I have question that, we shoud create new feature for each screen or not? because we have pages, widgets for each feature. How do we divide project to features easily?

@Reso Coder Great explanation....but I have a question. If I got 2 features then do I have to create all folders again for 2 different features? Like do I have to create 2 data folders, domain and presentation folders?

thanks bro, im Peruvian

Thanks so much for this course, thanks for Get_It, thanks for the model. I'm converting my app into this model.

Hello sir ! As u have created feature folder. if i have login, register, edit profile so have to create different folder for each? and having the same stuff(folders) as number trivia folders have?

Very Helpful. I have a question! There is a features folder in your folder structure and you built a small app with only one feature number_trivia(number_trivia is the name of application and also the name of the feature). What is the folder structure if we have more than one feature? for example "login" and "number_trivia". Should we have two folders inside "features" folder and each folder has its three layers?(it means number_trivia inside features folder, is the name of the feature). or we have only one folder named number_trivia inside features folder and it has all login and Number Trivia api requests and ui inside it? (it means number_trivia inside features folder is the name of application)!

Thanks for starting a series like this:D I will try to adopt your methodology. However you did not talk about testing at all in this video?

A more complex app would have many features that potentially share the same entities and data. Should those directory structures be up a level, outside the feature tree?

I stumbled upon the channel by accident, glad I did! Nice stuff!! I do, however have a question. Usually when you go to Clean you end up placing your Business Logic inside your domain so you can eventually reuse it, this (for me) meant that your BLoCs should be a part of that domain layer, however you place them within the Presentation Layer, what is your main reason? My guess is that since it is updating the UI like a Viewmodel would do then you are placing it with the screen/view that it is working with. Again, nice channel and tuts.

Which icon theme are you using for folders in project structure (VS Code)? 😍

I was following this course and implementing whatever was suggested in these 14 videos as it seemed to be amazing ... Then I wanted to dig more into the clean architecture and understand what was actually about. By watching the Unkle's Bob videos I could quickly understand that many things in this course were not actually following unkles bob concepts. One of those is widely using libraries. The purpose of Clean architecture is to keep everything segregated. This is not meant just between the objects inside our app but also from outside world libraries... dartz , get_it , flutter_bloc don't bring that many advantages. I can't see why we should use them. Conclusion: I am happy with the things that I have learned from this course "example unit testing and segregation of classes" but extremely unhappy with the overuse of libraries ... Now I need to rework my project as I have some problems with the flutter block and the way it works. Likely I didn't use get_it , the inheritedWidget works fine.

after 3 years what would you change in the layering/state management/separation that you proposed here ?

So i have to put up all those folders for each screen? Like say dashboard, profile, settings or any screen?

Are those features meant to be independent of each other? And if yes, there would be code duplication. What is the best approach in your opinion?

How do you make the folders look differently depending on how you name them? What plugin is that?

In which layer or where would you put the providers? are those below repository?

Would a mapper substitute the inheritance of models from the entities? (I believe it creates betters separation of concerns)

Hey, I love this video series and now I am using this architecture pattern for all of my apps. It makes it easier in reading and manages the code for larger projects. But I found that this pattern is less effective for only client-side-based apps like trivia apps, image editing apps, and todo apps. What architecture would you suggest for these types of applications? Please make a video series on that

What categorizes as a 'feature'?