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 :

🌐 Telegram Community

⚡ SUBSCRIBE HERE⚡

🌐Social Media

#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

[shamshushaash]

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

[hayk.galstyan]

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

[SyntacOps]

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

[niulkuu]

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!

[rrrrra]

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

[claytonliusemsve]

you are awsome guy! I love your flutter tutorial truely

[nipunshah]

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

[suryaishnavi]

Looking forward for projects in clean Architecture using bloc state management

[senmi]

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

[CharlesSteinmetz]

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!

[squidproxy]

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

[viewer]

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

[nebiberke]

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

[duongtruong]

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

[joshuanwokoye]

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

[rjrnxtm]

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

[Hazara_boy]

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

[semihylmaz]

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.