harmony 鸿蒙API Reference Document Description

2022-08-09
浏览 (1010)

API Reference Document Description

API references provide the description of APIs used for application development. This topic describes common fields in the API references to help you better use the reference document.

Version Description

In API references, the earliest versions of APIs and components are specified in the following ways:

For a new API or component, the version information is provided at the beginning of the reference document. Example: “The initial APIs of this module are supported since API version 7.”
For a new feature of an existing API or component, a superscript is added following the feature. For example, “uid⁸⁺” indicates that the uid attribute is supported since API version 8.

Application Model Description

Along its evolution, OpenHarmony has provided two application models: FA model and stage model. For their differences, see Interpretation of the Application Model.

If all the APIs of a module support only one model, the following description is provided at the beginning of the reference document: “The APIs of this module can be used only in the FA model.” or “The APIs of this module can be used only in the stage model.”
If certain APIs of a module support only one model, the following description is provided individually for these APIs: “This API can be used only in the FA model.” or “This API can be used only in the stage model.”
If both models are supported, no special description is provided.

Available APIs

Certain APIs provided by OpenHarmony are system APIs, which can be used only by original equipment manufacturers (OEMs) and cannot be used by common applications.

A description regarding system APIs will be provided in the document.

If all the APIs of a module are system APIs, the following description is provided at the beginning of the reference document: “All the APIs of this module are system APIs.”
If a specific API of a module is a system API, the following description is provided individually for the API: “This is a system API.”

A common application is an application whose application type is hos_normal_app in the HarmonyAppProvision configuration file. hos_normal_app is the default value for project creation.

The public SDK, which does not include system APIs, is provided as standard in DevEco Studio. To use the system APIs, you must: - Switch the public SDK to the full SDK by following the instructions provided in Switching to Full SDK. - Change the value of app-feature in the HarmonyAppProvision configuration file to hos_system_app (indicating a system application). For details, see HarmonyAppProvision Configuration File.

Permission Description

By default, applications can access limited system resources. However, in some cases, an application needs to access excess data (including personal data) and functions of the system or another application to implement extended functions. For details, see Access Control Overview.

To call APIs to access these resources, you must apply for the corresponding permissions by following the instructions provided in Access Control Development.

If an application can call an API only after it has obtained a specific permission, the following description is provided for the API: “Required permissions: ohos.permission.xxxx”
If an application can call an API without any permission, no special description is provided.

To determine whether an application can request a specific permission, see Applying for and Using a Permission.

System Capability Description

System capability refers to a relatively independent feature in the operating system. Different devices provide different system capabilities, and multiple APIs implement a system capability. You can determine whether an API can be used based on system capabilities. For details, see SystemCapability.

The following description is provided for each API in the reference document to describe the system capability of the API: “System capability: SystemCapability.xxx.xxx”

You can use the SystemCapability List to query the devices supported by a specific capability set.

Deprecated API Description

A deprecated API is an API no longer recommended and is marked with the ^deprecated superscript.

While deprecated APIs can still be implemented in the five API levels immediately following the version when the API is deprecated, this is not recommended.

Do not use deprecated APIs in new code. If possible, rewrite old code by replacing the deprecated APIs with their substitutes.
If no substitute is available, change the implementation mode by referring to the deprecation description and changelog.

Sample Code Language Description

OpenHarmony supports two development languages: JS and TS.

When a code block is labeled with js, the sample code can be used in the JS and ArkTS projects.
When a code block is labeled with ts, the sample code can be used only in the ArkTS project.