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
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!
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!
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
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.
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.
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. 👍👍👍
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
Glad it was helpful!
This is the best example of clean I've ever seen even outside of flutter... Impressive!
Wow, thanks!
These type of contents are very unique, Looking forward for projects in clean Architecture
Glad it was helpful!
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!
Glad it was helpful!
Awesome work, so timely now that I'm studying Code with Andreas article about Riverpod Architecture.
Glad it was helpful!
My absolute respect for this absolutely valuable video! Probably the best video on clean architecture that I have seen.
Glad you enjoyed it!
What's the difference between entity and models ? Would be great if you provide sample codes.
Hi bro, amazing explanation of this topic!
There is a software or plugin that helps to create the kind of animation you had used in this video?
good explanation, thanks
Looking forward for projects in clean Architecture using bloc state management
Truly crisp and totally informative video !
Great if it would be exemplified with small example !
Glad you liked it!
where does the bottom navigation tab fit in this design pattern maybe the core ? and thanks for the video
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!
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.
This video is so great
Thanks sir
master piece 👌
In Clean Architecture, when different features need to use the same API access code in the same data layer, what should be done?
Create a shared folder and put inside it
you are awsome guy! I love your flutter tutorial truely
Thank you so much 😀
❤
Very well done and explained.👍
Glad it was helpful!
Nice content, but it seems like there will be so many folders when using clean architecture
Is this architecture portable in other framework or is it Flutter specific ?
great
Could you please give us to flutter sample project RUclips video, about "clean architecture" in Flutter with database ?
We are planning about it. Soon you will get it. 👍👍👍
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
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.
🙏🙏🙏
Where you put Shared folder?
The folders in core do the same work as shared libraries
Are the admins of the channel from Pakistan and Iran? 😮
Yes
@@flutterguys ❤️
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.
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. 👍👍👍