The first stage, after decompression, there was a non-executable APK as the program entrance to connect with AOSP file libraries of binaries to interact with AOSP base of HarmonyOS 2.0 API 6, which is caused by the imperfect ecology of the early development of the new app file format during dual framework of OpenHarmony L3-L5 that consists of EMUI Android base convergence.

[7] Both HAR and HSP enable sharing of code, C++ libraries, resources, and configuration files.

In contrast, HSP allows independent compilation, leading to only one copy of code and resources in the build product.

[7] When multiple HAPs reference the same HAR, the HSP can be used instead to share some state variables and reduce the size of an App Pack.

[7] On OpenHarmony 4.1 API 11 improvements with System-level HSP that supports OTA upgrades within the App Package Management system.