src > main > module.json5: module configuration file in the stage model, which describes the global configuration of your app/atomic service, device-specific configuration, and HAP configuration. For details, see module.json5 Configuration File.
src > mock: mock capability of the test framework. For details, see Mock.
src > ohosTest: instrument test classes (storage directory). For details, see Instrument Test.
src > test: local test classes (storage directory). For details, see Local Test.
build-profile.json5: current module information and build configuration options, including buildOption and targets.
hvigorfile.ts: module-level build script.
obfuscation-rules.txt: obfuscation rule file. With the obfuscation feature enabled, the code will be compiled, obfuscated, and compressed during builds in release mode to protect code assets. For details, see Using Obfuscation for Code Hardening.
oh-package.json5: bundle name, version, entry file (type declaration file), and dependencies.

oh_modules: information about third-party library dependencies, including third-party library files on which the app/atomic service depends.
build-profile.json5: app-level configuration information, including the signature and product configuration.
code-linter.json5: code check rule configurations, including the code check scope and effective rules.
hvigorfile.ts: app-level build script.
oh-package.json5: global configuration, including overrides, overrideDependencyMap, and parameterFile.
oh-package-lock.json5: app-level dependent version locks and cache metadata of the dependencies.

Directory	Resource File Description
base > element	JSON file that contains resources such as character strings, integers, colors, and styles. Each resource is defined in JSON format, including: boolean.json color.json float.json intarray.json integer.json pattern.json plural.json strarray.json string.json
base > media	Multimedia files, such as graphics, videos, and audios. Supported file formats include .png, .gif, .mp3, and .mp4.
rawfile	Raw resource files in any format. rawfile does not look for resources based on the device status. You need to specify the directory, including the file name, for reference.

C++ Project Directory Structure (Stage Model)

C++ projects in the stage model support API version 10 and later and can be developed using a combination of ArkTS and C++. The project directory is shown below.

entry: app module, which can be built into a HAP.

libs > {abi}: .so files, which are packaged into the build product package by default. {abi} indicates the CPU architecture type of the device (for example, arm64-v8a).
src > main > cpp > types: a collection of C++ API description files.
src > main > cpp > types > libentry > index.d.ts: file that describes the C++ API behavior, such as the API name, input parameters, and output parameters.
src > main > cpp > types > libentry > oh-package.json5: configuration of the entry to the .so third-party package declaration file and third-party package names.
src > main > cpp > CMakeLists.txt: CMake configuration file, which provides CMake build scripts.
src > main > cpp > napi_init.cpp: file that defines C++ APIs.
src > main > ets: a collection of ArkTS source code.

src > main > resources: a collection of resource files used by your app, such as graphics, multimedia, character strings, and layout files. For details about resource files, see Resource Categories and Access.

Directory	Resource File Description
base > element	JSON file that contains resources such as character strings, integers, colors, and styles. Each resource is defined in JSON format, including: boolean.json color.json float.json intarray.json integer.json pattern.json plural.json strarray.json string.json
base > media	Multimedia files, such as graphics, videos, and audios. Supported file formats include .png, .gif, .mp3, and .mp4.
rawfile	Raw resource files in any format. rawfile does not look for resources based on the device status. You need to specify the directory, including the file name, for reference.

JS Project Directory Structure (FA Model)

JS projects can only be built in the FA model. The following figure shows the project directory structure.

entry: app/atomic service module, which can be built into a HAP.

src > main > js: a collection of JavaScript source code.
src > main > js > MainAbility: entry to your app/atomic service.
src > main > js > MainAbility > i18n: resources in different languages, for example, UI strings and image paths.
src > main > js > MainAbility > pages: pages contained in MainAbility.
src > main > js > MainAbility > app.js: ability lifecycle file.

src > main > resources: a collection of resource files used by your app/atomic service, such as graphics, multimedia, character strings, and layout files. For details about resource files, see Resource Categories and Access.

目录

Project Directory Structure

ArkTS Project Directory Structure (Stage Model)

C++ Project Directory Structure (Stage Model)

JS Project Directory Structure (FA Model)