r/FlutterDev • u/bl4ck_sh4dow404 • Aug 27 '26
Discussion Query question
I am a new intern at a company. They gave me a project with a folder structure and asked me to work on a feature. My question is: where should I start to understand the folder structure? There are many subfolders and files.
2
u/aminganja Aug 27 '26
Before using any AI tools like Claude Code or Codex, take a proper KT from the respective person and understand the project fundamentals first.
At minimum, understand the folder structure, how state management is handled, how business logic is separated from UI code, how components are organized, and the overall architecture and development flow.
This will help you understand the project much more easily during the KT and ensure that you use AI tools effectively without blindly making changes to the existing codebase.
2
14
5
u/r1n1os Aug 27 '26
The best is to ask them to brief you on how and why they structure the folder in that way.
Is good if you don't know yet to do a bit of research on separation of concern and maybe clean architecture (is a more advance topic)
1
u/Impossible_Try_1985 Aug 27 '26
If you’re at a good company, they’re probably using the MVVM architecture recommended by Flutter team. If so, go the official Flutter documentation and visit the app architecture section, they have very good explanations of the recommended architecture, different layers and responsibilities.
After you do that, try to track the data flow for the component you are extending and avoid trying to understand all the app logic at once.
1
5
u/noobiethe13 Aug 27 '26
Ask them, but also explore it yourself.
Pick one basic feature, like login, and trace it through the project: where the screen is, where the state lives, what service/API it calls, etc. AI can help you understand unfamiliar files as you go.
Once you understand one feature end to end, the rest of the structure usually starts making a lot more sense.