Application- or Component-Level Configuration (Stage Model)

During application development, you must configure tags to identify an application, such as the bundle name and application icon. This topic describes some critical tags.

Configuring the Bundle Name

The bundle name is specified by the bundleName field in the app.json5 file in the AppScope directory of the project. This field identifies an application and must be globally unique. You are advised to use the reverse domain name notation, for example, com.example.demo, where the first part is the domain suffix com, the second part is the vendor/individual name, and the third part is the application name, which can be of multiple levels.

Configuring the Application Icon and Label

Application icons and labels are usually configured together. They correspond to the icon and label fields in the app.json5 file and module.json5 file. Starting from DevEco Studio 5.0.3.800 and later, the icon and label fields in the module.json5 file are no longer mandatory. However, they are mandatory in the app.json5 file. Therefore, they can be omitted in the module.json5 file. There is a priority and effectiveness strategy for the icon and label fields in both the app.json5 and module.json5 files. For details, please refer to Configuration Priority and Build Policy.

Configuring Application Version Declaration

To declare the application version, configure the versionCode and versionName fields in the app.json5 file in the AppScope directory of the project. versionCode specifies the version number of the application. The value is a 32-bit non-negative integer. It is used only to determine whether a version is later than another version. A larger value indicates a later version. versionName provides the text description of the version number.

Configuring Device Types Supported by the Module

To configure the device types supported by the module, set the deviceTypes field in the module.json5 file. If a certain device type is added to deviceTypes, the module can run on that device.

Configuring the Module Permission

The requestPermissions field in the module.json5 file is used to configure the permission information required by the module to access the protected part of the system or other applications. This field declares the name of the permission to request, the reason for requesting the permission, and the scenario where the permission is used.

Configuring the Launch Mode

From API version 20 onwards, the startMode field can be used to customize the mode for starting an application upon an icon tap. This setting takes effect only when launchType is set to singleton and is designed for applications with multiple UIAbility components. The startMode field must be specified in the app.json5 file.

• The default value is mainTask, indicating that the main UIAbility of the application is always started when the icon is tapped.
• The value can be recentTask, which means that the most recently used UIAbility is started when the icon is tapped.

{
  // ...
  "app": {
    "startMode": "mainTask"
    // ...
  }
}