@@tadaspetra yes I really want to hear more from you. I request you to make a video on Best Practice in flutter and how to optimize an app. How can we design a responsive design in flutter. These are my requested topic. Kindly make a video when you have time. :)
Hammad Pervez I’ve been wanting to make a best practices. But I want to double check that they’re not just my personal best practices. But also universally accepted for flutter
I really like this structure so far, it works for most of my cases. I always add a scripts folder for more significant projects, where I put some of my SH Scripts inside so that I can create for example keys for internationalisation.
The only drawback of this approach is when the app grows there would be numerous files inside models, services, screens etc. It would be hard to navigate or to understand which feature maps to which classes or functionalities. I would have something like this. Lib - global - models - services - utils - widgets - features - home - widgets - services - models - login - services - models - widgets Etc What do you think about this folder structure?
Typing on the phone.. not sure whether the folder structure has come out right. Basically the idea is to group all the global classes under a folder and others based on features. Improves readability I feel.
That’s a good file structure and common for small to medium apps. I don’t agree it suits very large projects cause the coupling of concerns will make maintainability harder. Large projects with several developers will benefit from having a microfronted instead of a big monolithic with 40+ models in the same folder.
If you are talking about large projects with high coupling not being maintainable, I think that is a concern with the application architecture. Architecture should push for low coupling and high cohesion. I hope I'm understanding your point correctly. As for projects with lots of models I would definitely recommend to organize that a bit more, but I would think that could be done within the models folder as well. Do you have any examples or something that would be a better structure for larger projects? I would love to see it and improve the way I organize :) Anyway thanks for the feedback!
Folder structure is part of the architecture and means a lot for the liability that project is carrying on. I thinks that a modular structure just like feature modules works in android will work in situations like this. Another thing that I don’t agree is in having a widgets/ folder, when everything in flutter is a Widget, it may not be obvious where to create a widget (inside my screens/onboarding/or inside widgets/), this can cause the separation of concern I was talking about, meaning that code that is suppose to be related (and close) is now split across different places. Also note that your folder structure would be a go to for me and it is similar to the one I use in my projects. For large projects I would rethink depending on the team and business we are solving. There is no a 1 size fits all
I agree that modular structure would be a good way to do it as well. As for my widgets/ folder that is more of a "global widgets" or widgets used throughout the app. I usually put things like an app bar that is consistent throughout most of the screens, post format, things like that. Any local widgets, that are only used in one screen I tend to keep them within the screen folder so the scope isn't any bigger then it needs to be. In the widgets/ (aka global widgets) folder I put things that are related to parts throughout the app. So it wouldn't really make any sense to put it in a specific screens folder. And the last part I definitely agree on, before starting a big project with a team, a lot of factors need to be accessed including what folder structure fits best for the project. I think I mentioned in the video that this isn't a perfect solution for all scenarios and should be amended to fit the project. (i just checked and i had mentioned that in the description, not in the video)
Brian Dunn I have gone through a whole state management journey since this video with almost all the state management solutions it seems 😂. But with provider I set up a “providers” folder as well. And then I also use GetX in the newer videos and there I have a “controllers” folder which is pretty similar
No I don’t necessarily think that’s a good idea. I would take a look at some newer state management videos especially with Riverpod. The functions related to managing your state should be within your provider(specifically statenotifierprovider) but methods are usually pretty different throughout the apps. But if you do have some that are used throughout having something like in the utils folder would be good
@@tadaspetra thanks for the answer, using Riverpod, so cool - been doing that with my methods actually as you say but could be better. Your video has helped me feel much better about managing a larger project.
I would create feature folders first and then put controllers, services and the other layer-files for that features in there. What structure do you like?
Do you do this writing stuff on a tablet? I wonder if i have android phone and like windows 10's onenote better can i use my phone as a touch surface for windows and that too like a tablet?
TECH STUDIO I have a Lenovo x1 yoga. So it makes it pretty easy to do things like this. It has a touch screen and comes with a pen. And I’m not too sure how that would work with the phone as the touch input. But it sounds like it could be possible. Give it a shot!
So the functions, assets, and fonts are on the same level, outside of the lib folder. These are because it's not directly tied to the app and how it works and rather just pieces that the app uses
Thank you. I appreciate it! But I've tried both Bloc, and provider. And in the current book club app I'm building I use Provider and I think I like it so far!
hello sir please help to solve my issue Android toolchain - develop for Android devices ✗ Unable to locate Android SDK. Install Android Studio from developer.android.com/studio/index.html On first launch, it will assist you in installing the Android SDK components. (or visit flutter.dev/docs/get-started/install/macos#android-setup for detailed instructions). If the Android SDK has been installed to a custom location, set ANDROID_SDK_ROOT to that location. You may also want to add it to your PATH environment variable.
One of the best video about how to structure an app in easiet way and amazing illustration
Hammad Pervez thanks man I appreciate it. I feel like I gotta get back to doing more illustrations to help explain some of the topics
@@tadaspetra yes I really want to hear more from you.
I request you to make a video on Best Practice in flutter and how to optimize an app. How can we design a responsive design in flutter. These are my requested topic. Kindly make a video when you have time. :)
Hammad Pervez I’ve been wanting to make a best practices. But I want to double check that they’re not just my personal best practices. But also universally accepted for flutter
I really like this structure so far, it works for most of my cases. I always add a scripts folder for more significant projects, where I put some of my SH Scripts inside so that I can create for example keys for internationalisation.
Sounds like a necessity for scripting. I haven't done much scripting for flutter, but i will definitely look into it
The Slav Squat
I see you nailed it
hey you been practicing for years 😂
Your video is help me a lot. This is great structure. Thank you sir. from south korea in seoul.
Your video helped me a lot. Thank you!!!
No problem! Glad it helped!
Thanks for share your knowledge my friend!.
Leon Martinez thank you for watching!
Thanks for share , One of the best video about how struct an app in easiest way *_*.
Thank you! Really appreciate it
Thank you for sharing
One word: Awesome!
thank you so much. This video useful for me
Thank you for watching. 😊
Such a good video, thanks!
Thanks for watching 😊
Great video, loved it.
Your explanation made me subscribe. I love the way you take your time to explain. Awesome🔥
Ronald Dumeloo thank you 🙌 and yes I really like to break it down so others and myself can really understand
Thanks very much
Great video, thanks.
MultiECommerce thanks for watching
loved this video...thank you
thank you for watching!
@@tadaspetra it was totally my pleasure...
The only drawback of this approach is when the app grows there would be numerous files inside models, services, screens etc. It would be hard to navigate or to understand which feature maps to which classes or functionalities.
I would have something like this.
Lib
- global
- models
- services
- utils
- widgets
- features
- home
- widgets
- services
- models
- login
- services
- models
- widgets
Etc
What do you think about this folder structure?
Typing on the phone.. not sure whether the folder structure has come out right. Basically the idea is to group all the global classes under a folder and others based on features. Improves readability I feel.
Cool
Thanks bro
Thank you for watching
Good video
Uday Garg thank you 🙌
Your video is help me a lot . This is great structure. Thank you sir.
No problem! Glad it could help!
Cool.
That’s a good file structure and common for small to medium apps. I don’t agree it suits very large projects cause the coupling of concerns will make maintainability harder.
Large projects with several developers will benefit from having a microfronted instead of a big monolithic with 40+ models in the same folder.
If you are talking about large projects with high coupling not being maintainable, I think that is a concern with the application architecture. Architecture should push for low coupling and high cohesion. I hope I'm understanding your point correctly.
As for projects with lots of models I would definitely recommend to organize that a bit more, but I would think that could be done within the models folder as well.
Do you have any examples or something that would be a better structure for larger projects? I would love to see it and improve the way I organize :)
Anyway thanks for the feedback!
Folder structure is part of the architecture and means a lot for the liability that project is carrying on. I thinks that a modular structure just like feature modules works in android will work in situations like this.
Another thing that I don’t agree is in having a widgets/ folder, when everything in flutter is a Widget, it may not be obvious where to create a widget (inside my screens/onboarding/or inside widgets/), this can cause the separation of concern I was talking about, meaning that code that is suppose to be related (and close) is now split across different places.
Also note that your folder structure would be a go to for me and it is similar to the one I use in my projects. For large projects I would rethink depending on the team and business we are solving. There is no a 1 size fits all
I agree that modular structure would be a good way to do it as well.
As for my widgets/ folder that is more of a "global widgets" or widgets used throughout the app. I usually put things like an app bar that is consistent throughout most of the screens, post format, things like that. Any local widgets, that are only used in one screen I tend to keep them within the screen folder so the scope isn't any bigger then it needs to be. In the widgets/ (aka global widgets) folder I put things that are related to parts throughout the app. So it wouldn't really make any sense to put it in a specific screens folder.
And the last part I definitely agree on, before starting a big project with a team, a lot of factors need to be accessed including what folder structure fits best for the project. I think I mentioned in the video that this isn't a perfect solution for all scenarios and should be amended to fit the project. (i just checked and i had mentioned that in the description, not in the video)
Finally, something simple. Thanks.
Do you use providers for state management? If so, where do you store them? Do you just put them in the models folder?
Brian Dunn I have gone through a whole state management journey since this video with almost all the state management solutions it seems 😂. But with provider I set up a “providers” folder as well. And then I also use GetX in the newer videos and there I have a “controllers” folder which is pretty similar
Good video :D
Mitzuko Davis thank you!
I love this method. Thank you !
Good video.
Thank you, I appreciate it!
Thanks a lot ❤
Great and simple structure ❤
Is it a also a good to localise methods in a "methods" folder, as well as your providers maybe?
No I don’t necessarily think that’s a good idea. I would take a look at some newer state management videos especially with Riverpod. The functions related to managing your state should be within your provider(specifically statenotifierprovider) but methods are usually pretty different throughout the apps. But if you do have some that are used throughout having something like in the utils folder would be good
@@tadaspetra thanks for the answer, using Riverpod, so cool - been doing that with my methods actually as you say but could be better. Your video has helped me feel much better about managing a larger project.
For small projects this is ok. but i wouldn't personally use this for big projects even for medium one.
I would create feature folders first and then put controllers, services and the other layer-files for that features in there. What structure do you like?
Thank you for your video. For Flutter we should use the BLOC Design Pattern. Do you think this will not fit for larger projects?
I think bloc works just fine for bigger projects. I personally prefer riverpod. But I got no problem with bloc
Do you do this writing stuff on a tablet? I wonder if i have android phone and like windows 10's onenote better can i use my phone as a touch surface for windows and that too like a tablet?
TECH STUDIO I have a Lenovo x1 yoga. So it makes it pretty easy to do things like this. It has a touch screen and comes with a pen. And I’m not too sure how that would work with the phone as the touch input. But it sounds like it could be possible. Give it a shot!
function directory under assets and font ( can y explain more the his utility )
So the functions, assets, and fonts are on the same level, outside of the lib folder. These are because it's not directly tied to the app and how it works and rather just pieces that the app uses
Hi, what is the name of this software that you drew in it?
it is Microsoft OneNote
hello, it is a superbe way to organize the project, so thank you ! Do you use BLoC state management or using setState for screens ?
Thank you. I appreciate it! But I've tried both Bloc, and provider. And in the current book club app I'm building I use Provider and I think I like it so far!
@@tadaspetra Looking forward for Provider AND Riverpod!
What hardware and software do you use to draw like this?
CodeBit I use OneNote. And the laptop is a Lenovo X1 Yoga so it comes with a touchscreen and a pen
@@tadaspetra Thanks for the answer, and the video. :)
hello sir please help to solve my issue
Android toolchain - develop for Android devices
✗ Unable to locate Android SDK.
Install Android Studio from developer.android.com/studio/index.html
On first launch, it will assist you in installing the Android SDK components.
(or visit flutter.dev/docs/get-started/install/macos#android-setup for detailed instructions).
If the Android SDK has been installed to a custom location, set ANDROID_SDK_ROOT to that location.
You may also want to add it to your PATH environment variable.
Came here after bitfumes
Wow that is awesome thank you!!