HarmonyOS has grown into a platform developers can no longer ignore, particularly when targeting users in China. With Huawei shipping HarmonyOS NEXT on newer devices — a version that runs HarmonyOS-native apps rather than Android ones — understanding how app distribution works in this ecosystem is now part of any serious China-market release plan. This guide covers the essentials.

Two things called "HarmonyOS"

First, a key distinction. Older HarmonyOS versions could run Android APKs alongside HarmonyOS-native apps. HarmonyOS NEXT dropped the Android compatibility layer, so on those devices only HarmonyOS-native apps run. This means "distributing to HarmonyOS" increasingly means shipping a native HarmonyOS app — not just an APK that happens to install. For developers, the practical implication is that a pure-Android APK strategy will miss HarmonyOS NEXT users.

The package formats: .hap and .app

HarmonyOS apps are packaged differently from Android:

  • .hap (Harmony Ability Package) — the basic unit of a HarmonyOS module. A single-feature app may be one HAP; a complex app is several HAPs.
  • .app — a complete app bundle made up of one or more HAPs, used for publishing to AppGallery.

Developers build these in Huawei's DevEco Studio IDE using ArkTS (the language for HarmonyOS-native development) and the ArkUI framework.

The store: Huawei AppGallery

AppGallery is Huawei's app marketplace and the primary channel for distributing HarmonyOS apps. Publishing requires a Huawei developer account, a signed package, and review for compliance. AppGallery serves both Android (APK/AAB for Huawei devices still on Android-compatible firmware) and HarmonyOS-native apps, making it the single most important store for the Huawei and HarmonyOS audience.

HAG: HarmonyOS Ability Guaranteed / quick services

HarmonyOS also introduces lightweight "quick apps" / services that users can run without a full install — surfaced through system widgets, the service center, and search. For some use cases (a quick lookup, a form, a mini-tool), a service widget reaches users with even less friction than an installed app. Whether to invest in these depends on your app's purpose.

Signing and certificates

Like iOS, HarmonyOS requires a developer certificate and profile. You create a debugging certificate for testing on real devices and a release certificate for AppGallery submission. Huawei's signing process is managed through the AGC (AppGallery Connect) console. Plan for this lead time the first time you publish — certificate generation and profile setup are not instantaneous.

Reaching HarmonyOS users from one link

Because HarmonyOS devices sit alongside Android and iOS in the real world, a unified distribution link needs to recognize them. The User-Agent on HarmonyOS contains HarmonyOS and/or ArkWeb tokens. A smart install page detects these and routes the visitor to AppGallery (or a direct .hap download for internal testing), while routing Android users to their OEM store and iOS users to TestFlight or an OTA page.

Treating HarmonyOS as a first-class platform in your device-detection logic — not a fallback under "Android" — is what lets one QR code serve Huawei, HarmonyOS, and everyone else.

Distribution checklist for a China-market release

  • Build a HarmonyOS-native app for HarmonyOS NEXT devices (ArkTS / DevEco Studio).
  • Publish to AppGallery with a release certificate and completed store listing.
  • Keep an Android APK/AAB for Huawei devices still on Android-compatible firmware and for other OEM stores (Xiaomi, OPPO, VIVO, Honor).
  • Use a unified link + QR code that detects HarmonyOS and routes to AppGallery automatically.
  • Consider a service widget if a lightweight, no-install experience fits your use case.

What about updates?

Updates for AppGallery-distributed apps are delivered through the store, just like other platforms. For internal HarmonyOS testing, hosting the .hap/.app on a private download page lets you iterate fast without a store review cycle — the same pattern as internal iOS/Android distribution, just with HarmonyOS packages.

Conclusion

HarmonyOS is now a distinct distribution target with its own package formats, store, and signing model — not merely another Android skin. For teams targeting China, building a HarmonyOS-native app, publishing it on AppGallery, and wiring it into a unified smart-routing link ensures Huawei and HarmonyOS users reach your app as easily as everyone else. The investment is real, but so is the audience it unlocks.