Production grade Flutter Architecture with Riverpod

Github Repo :
github.com/dartbucket/flutter...
email us :
[e-mail]
In this tutorial, we will learn how to architect a Flutter project. We will cover topics such as:
Creating a clean and organised project structure
Using state management to keep your code DRY
Building reusable components
By the end of this tutorial, you will have a solid understanding of how to architect a Flutter project that is easy to maintain and extend.
Here are some of the benefits of architecting your Flutter project correctly:
Easier to maintain: A well-architected project is easier to maintain because it is easier to understand and navigate.
Easier to extend: A well-architected project is easier to extend because it is easier to add new features and functionality.
More efficient: A well-architected project is more efficient because it is easier to debug and optimise.
Better performance: A well-architected project can perform better because it is easier to optimise for performance.
If you are serious about building great Flutter apps, then it is important to learn how to architect your projects correctly. This tutorial will give you a solid foundation on which to build your skills.
#flutter #tutorial #android #vscode #google #fluttertutorial #fluttertutorialforbeginners #fluttertutorial2023

[@roninspect4357]

i use that structure, feeling relieved that other developer also adopting this structure.

[@moammarqaddafi4858]

This looks great

[@yooscripts5947]

Useful video thanks

[@KyoYamamoto-rc5jp]

Good content

[@rijvanahmad8272]

Good job Sir

[@dartbucket]

Thanks

[@nipunshah1373]

+1 for custom architecture.
Just few doubts :-
1. model aint also belong to respective features ?
2. the api implementation should be somewhere else out of core, as it is external things (ie Infra) ?

[@roninspect4357]

maybe because same model can be used for different feature

[@dartbucket]

Well you can definitely make separate API implantations depending upon use case. This architecture works well as long you're having simple GET, POST, PUT and DEL requests.
For models you can put them their respective features dir if it's a bigger project.

[@mandarkhandagale4367]

Nice Architecture bro. Just one doubt can we have a model class folder at feature level??

[@dartbucket]

Yes you can. That's all up to you. Whatever makes development easier and robust.

[@roninspect4357]

an fully functional API based app with that architecture would be great

[@dartbucket]

Thanks! super excited to know what you're building ✌️

[@hurbangash1302]

@@dartbucket he is asking you to make tuts

[@shadyarbzharothman8689]

Is there any resource that I can learn this architecture for riverpod from?

[@dartbucket]

You can find projects here riverpod.dev/

[@shadyarbzharothman8689]

Thanks@@dartbucket

[@vasanthmn]

code is not working

[@dartbucket]

Please connect with me
instagram @dartbucket