Clean Architecture in Flutter - All You Need to Know!

📄Architecture is very important in developing an application. Architecture can be likened to a floor plan that describes how the flow in an application project. The main purpose of implementing the architecture is the separation of concern (SoC). So, it will be easier if we can work by focusing on one thing at a time.
In the context of Flutter, clean architecture will help us to separate code for business logic with code related to platforms such as UI, state management, and external data sources. In addition, the code that we write can be easier to test (testable) independently.
🤖About AI - Please Subscribe :
🔗 / @theaionline
🌐 Telegram Community
🔗 t.me/flutterguysgp
⚡ SUBSCRIBE HERE⚡
🔗 cutt.ly/2XkZz0X
🌐Social Media
🔗 Linkedin: / mahdinazmi
🔗 GitHub: github.com/mahdinazmi
🔗 Twitter: / flutterguys1
#flutter #fluttertutorial #flutterwidgets #fluttercourse #flutter2023 #flutterroadmap

[@NadaHasni]

this is the most easy to digest clean architecture tutorial on youtube! You're channel is so underrated. This deserves more recognition! Thank you for these amazing tutorials

[@flutterguys]

Glad it was helpful!

[@hayk.galstyan]

This is the best example of clean I've ever seen even outside of flutter... Impressive!

[@flutterguys]

Wow, thanks!

[@shamshushaash5251]

These type of contents are very unique, Looking forward for projects in clean Architecture

[@flutterguys]

Glad it was helpful!

[@SyntacOps]

My absolute respect for this absolutely valuable video! Probably the best video on clean architecture that I have seen.

[@flutterguys]

Glad you enjoyed it!

[@user-ni4ul7ku8u]

Great video on Clean Architecture in Flutter! It's always great to see practical examples of how to apply software architecture principles in real-world scenarios. I appreciate how the presenter explained the importance of separation of concerns and how it can lead to more maintainable and scalable code. The examples and diagrams helped to illustrate the concepts clearly. Thanks for sharing this valuable information!

[@flutterguys]

Glad it was helpful!

[@maxkee2834]

This video is so great Thanks sir

[@rr2r2r2ra]

Awesome work, so timely now that I'm studying Code with Andreas article about Riverpod Architecture.

[@flutterguys]

Glad it was helpful!

[@barziyassin1]

master piece 👌

[@nipunshah1373]

Truly crisp and totally informative video ! Great if it would be exemplified with small example !

[@flutterguys]

Glad you liked it!

[@claytonliusem4sve826]

you are awsome guy! I love your flutter tutorial truely

[@flutterguys]

Thank you so much 😀

[@senmi6949]

What's the difference between entity and models ? Would be great if you provide sample codes.

[@matthiasimegi8211]

Very well done and explained.👍

[@flutterguys]

Glad it was helpful!

[@suryaishnavi]

Looking forward for projects in clean Architecture using bloc state management

[@squidproxy136]

where does the bottom navigation tab fit in this design pattern maybe the core ? and thanks for the video

[@user-kt2le3mr1s]

great

[@CharlesSteinmetz1]

thank you for this really nice video! I am looking forward to the next one on this topic. I am always a bit confused when features have to share code such as entities or repositories... do you guys have a resource I could learn more about it? (I am afraid I will end up adding all my code in the core folder since a lot of things are used throughout the app 😅) thank you!

[@flutterguys]

Glad it was helpful! You need to check others code. With a simple search on GitHub, you can check Flutter projects that use clean architecture.

[@trungtranthanh8912]

❤

[@viewer5099]

Is this architecture portable in other framework or is it Flutter specific ?

[@user-gx5mk2dm2d]

🙏🙏🙏

[@duongtruong7772]

i have a question why don't we use the same class domain/entities/ which datasources/models, i saw them pretty common, i don't know why we have to split it to 2 different class

[@flutterguys]

Domain layer must be independent. If we use entity in the data layer, we may have to change the entity due to changes in the API or database, and this is against the clean architecture and domain layer.

[@nebiberke]

In Clean Architecture, when different features need to use the same API access code in the same data layer, what should be done?

[@flutterguys]

Create a shared folder and put inside it

[@user-rj7rn2xt9m]

Could you please give us to flutter sample project KZbin video, about "clean architecture" in Flutter with database ?

[@flutterguys]

We are planning about it. Soon you will get it. 👍👍👍

[@baguskto]

Where you put Shared folder?

[@flutterguys]

The folders in core do the same work as shared libraries

[@joshuanwokoye]

Nice content, but it seems like there will be so many folders when using clean architecture

[@semihylmaz4936]

Nice video thanks for your effort 😊 I wanna say something about this. I love the practices Clean archirecture and feature based folder structure. But i don’t think they fit with each other that much. Let’s say “Auth” feature has a User model and usecase createUser. In the “Settings” feature we also need user model and delete functioned usecase with it. // Should i re-type User model and usecase ? No it’s too bad practice. // impoting auth/model in “Settings” feature ? Why “Settings” can not be a feature without “Auth” one. So some of layers should separated for example lib - - core - features-> presentation - app_layer -> data,domain I’m still thinking about it. If you know some good practices for this please share with us.

[@flutterguys]

I totally agree with you. Clean Architecture is just a concept of decoupling different layers. So create any folder structure which best suit in the scenario to keep the code DRY. 👍👍👍

[@Hazara_boy]

Are the admins of the channel from Pakistan and Iran? 😮

[@flutterguys]

Yes

[@Hazara_boy]

@@flutterguys ❤️