Glossary

A

ABC File

An ArkCompiler Bytecode (ABC) file generated by the ArkCompiler toolchain from source code. It uses the .abc file extension. In the release build, ABC files are packaged into the HAP.

AppLinking

A user acquisition service built on operating system capabilities such as Deep Links and URL schemes. If the target application is installed, users can be directed to specific content. Otherwise, developers can customize the destination. The service also ensures secure navigation by preventing target applications from being spoofed.

ArkCompiler

A built-in, modular, and configurable multilingual compilation and runtime platform for OpenHarmony. It consists of key components such as compilers, toolchains, and runtimes. ArkCompiler supports compiling and running high-level programming languages on a wide range of chip platforms, and enables the OpenHarmony standard operating system, together with its applications and services, to run on devices such as smartphones, PCs, tablets, TVs, vehicles, and wearables.

ArkTS

The application development language for the OpenHarmony ecosystem. Based on TypeScript (TS), ArkTS extends the language with capabilities such as declarative UI and state management, enabling developers to build applications in a simpler and more intuitive way.

ArkUI

The native UI framework for OpenHarmony. It is a lightweight, high-performance UI framework for developing cross-device applications, enabling developers to efficiently build user interfaces across devices.

B

Bundle Manager Service (BMS)

A system service that manages application packages.

C

Common Event Service (CES)

A system service responsible for publishing, subscribing to, and unsubscribing from common events.

D

Distributed Management Service (DMS)

A system service that provides distributed management capabilities.

E

ExtensionAbility

A component type in the Stage model that provides extension capabilities for specific scenarios, such as widgets and input methods, enabling a wider range of application scenarios.

F

FA Model

The application model supported in API version 8 and earlier. This model is no longer recommended. Use the Stage model instead.

H

Harmony Ability Package (HAP)

A file contains all the content of an application, including code, resources, third-party libraries, and application configuration files. It uses the .hap file extension.

Hardware Driver Foundation (HDF)

A hardware driver framework that provides unified peripheral access as well as a framework for driver development and management.

HDF Configuration Generator (HC-GEN)

A tool that converts HCS configuration files into a format that can be read by software.

HDF Configuration Source (HCS)

A configuration description language for the HDF driver framework. It uses a key-value-based text format to decouple configuration code from driver code and simplify configuration management.

Hypium

The name of the OpenHarmony automated testing framework. It is derived from "Hyper Automation" and "ium", where "ium" represents a stable and reliable testing framework foundation.

I

Intelligent Distributed Networking (IDN)

An OpenHarmony-specific distributed networking capability. Developers can use IDN to obtain the list and status of devices in a distributed network and subscribe to changes in their online status.

M

Module

A part of an application. Each module has its own module.json5 configuration file. In a project, Entry, Feature, HSP, and HAR are all application modules.

S

A component that displays important application information on the home screen in the form of widgets. Users can quickly access application services through intuitive gestures, reducing the need for multi-level navigation.

Stage Model

The application model introduced in API version 9. It provides two major component types: UIAbility and ExtensionAbility. The model is named Stage because it introduces classes such as AbilityStage and WindowStage that act as the "stage" for application components and windows.

Super Virtual Device

Also referred to as the Super Device, it integrates the capabilities of multiple devices through distributed technologies into a virtual hardware resource pool. Device capabilities can then be centrally managed and scheduled to provide services as needed.

System Capability (SysCap)

A SysCap identifies an independent feature provided by OpenHarmony, such as Bluetooth, Wi-Fi, or NFC. Each feature corresponds to one or more APIs, and each API is tagged with the corresponding SysCap.

System Type

Mini system: Designed for MCU (Microcontroller Unit)-based processors, such as Arm Cortex-M and 32-bit RISC-V devices. It targets devices with extremely limited resources (recommended memory: ≥128 KiB) and provides rich short-range connectivity and peripheral bus access capabilities. Typical products include smart home connectivity modules and sensor devices.
Small system: Designed for application processors such as Arm Cortex-A. It targets devices with at least 1 MiB of memory and provides enhanced security, a standard graphics framework, and multimedia capabilities such as video encoding and decoding. Typical products include IP cameras, smart peepholes, routers, and dashcams.
Standard system: Designed for application processors such as Arm Cortex-A. It targets devices with at least 128 MiB of memory and provides enhanced interaction capabilities, 3D GPU and hardware composition support, richer UI components and animations, and a complete application framework. Typical products include high-end refrigerator displays.

U

UIAbility

A component type in the Stage model that provides a user interface and serves as the primary component for user interaction.