 Hello guys, so today in this video, we are going to discuss about the basic project structure of Plutter project Okay, so first of all, you can see a lot of files and folders are there that start with a dot so you can basically Skip that because they are not most of the time useful So out of them whenever whatever we will use I will let you know the more detail So here the first one is start tools it basically contain the information about Dot build and whatever packages are there everything is there and This idea is basically a folder that is related to the configuration of this IDE that is VS code And then we have a Android folder. This is for Android specific source code and libraries Then we have a build folder. So this folder will be automatically generated whenever you try to create a build Like you are creating an APK file, then you will be able to find it over here So I will show you whenever we will generate a build and then we have iOS folder that contains iOS specific source code and the files Then we have live folder. So this is basically the main folder where we need to write the Flutter code So you can see the main dot file over here. Okay So then we have Linux folder that is for Linux specific code Then Mac OS that is for Mac OS specific code. Then we have a test for writing test cases and Then we have web or if you want to generate web specific code that would be generated over here Then we have Windows. So for Windows specific code, it would be here inside this folder Then this is git ignore which is used by the git the versioning control So whenever you want to push something into the repository if you don't want to push something then you can specify inside this So git command will ignore that then meta data is basically related to this Whatever version of the app whatever channel you're working on a lot of information is in then packages will contain some dependencies whatever we have already in the There's a pump Specure the ML file. So it is basically generated by that pump that is package manager Then we have analysis. This is basically a file that used for analysis. So here you can mention some rules which need to be followed by Writing the code. So basically it will cross check that rules So it is basically used for best coding practices. Okay, then we have this first app implement So basically you don't need to bother about this. Oh, it is again containing some components and modules These are auto generated. You don't need to bother about this Then we have this pub spec.log. So this is again a auto generated file You don't need to bother about this you can even delete it It would be generated automatically whenever you modify this pub spec dot file So this pub spec dot ml file is very important So here we mentioned the name of the project application the description Where you are publishing what is a version what on which environment it is going on and all the dependencies and other stuff So whenever we work with that dependency and other stuff, I will let you know how to use these Let's close it And the last one is readme.md. This readme.md file is very useful whenever we push our project on an Repository so there you must have seen some readme file. So that file is totally coming from this file So that's all for this video if you have any doubt inquiry do comment in the comment section. Thank you