1# Multi-HAP Build View 2 3 4DevEco Studio allows you to develop and build multiple HAP files in one application project, as shown below. 5 6 **Figure 1** Multi-HAP build view 7 8 9 10 111. Development view in DevEco Studio 12 - **AppScope** folder 13 14 - **[app.json5](app-configuration-file.md)**: stores application-wide configuration, such as the application bundle name, version number, application icon, application name, and dependent SDK version number. 15 - **resources** folder: stores application icon resources and application name string resources. 16 17 **NOTE** 18 19 - The folder is automatically generated by DevEco Studio and its name cannot be changed. 20 - The file names in the **AppScope** folder cannot be the same as those in the entry- or feature-type module folder. Otherwise, an error will be reported. 21 - **entry** or **feature** folder (whose name is customizable) 22 - A module folder created by the developer by following the creation wizard of DevEco Studio. It stores the service logic implementation of the application. Multiple module folders can be created. In the preceding figure, **entry** and **feature** are two created module folders. 23 - **resources** folder: stores the resources used by the module. 24 - **ets** folder: stores the service logic. 25 - **[module.json5](module-configuration-file.md)**: stores module configuration, such as the module name, entry code path of the module, and component information. 26 272. View after build and packaging 28 - After a module is built, a HAP file for deployment is generated. Each module corresponds to a HAP file. 29 - The **module.json** file in the HAP file is composed of the **app.json5** and **module.json5** files in the development view. 30 - All HAP files are finally built into an Application Package (App Pack) in .app format for release to the application market. 31
