To maintain the order of the Huawei notification ecosystem, protect users' legitimate rights, and deliver a premium user experience, these specifications are established in accordance with applicable laws and regulations, as well as HUAWEI Developers Service Agreement, Agreement on Use of Huawei APIs, HUAWEI Push Service Agreement, AppGallery Review Guidelines, and Atomic Service Review Guidelines.
All HarmonyOS apps, jointly-operated apps, and atomic services (hereinafter referred to as "apps") that are to be released on HUAWEI AppGallery and use Push Kit must adhere to the specifications. If you violate the specifications or the AppGallery Joint Operations Service Agreement, Huawei has the right to impose penalties on you in accordance with these specifications and the AppGallery Joint Operations Service Agreement.
Basic Principles for Using Push Kit
Push messages of HarmonyOS apps must be delivered through Push Kit (Huawei's official push channel).
The standard message layouts must be used to ensure consistent notification experience.
Message push requires user consent, and an app needs to ask users whether to allow notifications upon the first app launch.
It is prohibited to forcibly change the notification attributes for commercial purposes (for example, forcibly pin a notification to the top by re-using an ongoing notification), as this may compromise user experience.
Notification content management rules shall be complied with.
Notification Content
To ensure the legitimacy, authenticity, objectivity, consistency, and readability of the content sent through Push Kit, and to provide users with a premium notification experience, please comply with the notification content management rules.
[h2]Overview of Notification Layout Specifications
| General Principle | Exception |
|---|---|
| Do not forge push messages of other apps, including forging app icons and message content. | - |
| Do not hide your app icon in a notification. | - |
| Do not use a notification layout that is inconsistent with the design specifications. | - |
| Do not forcibly pin a specific notification to the top by re-using an existing ongoing notification. | Voice call, video call, media playback, progress notification (such as download, update, and upload), voice recording, navigation, screen projection, workout timer, and step count. |
| Do not modify the one-tap deletion button. | - |
| Do not forge banner notifications or lock screen notifications. | - |
| Do not send a same notification repeatedly to disturb users. | - |
| Ensure that the notification title is different from the notification body. | - |
[h2]Text Format
| Description | Image Display |
|---|---|
| A maximum of three lines can be displayed for the notification content. If the content is too long, it is truncated by an ellipsis (...). | For details, please refer to Styles for Common Notifications. |
[h2]Notification Badge
After receiving a message, the app displays a numerical badge on the app icon to remind users to view the message.
| Description | Image Display |
|---|---|
| The numerical badge is displayed in the upper right corner of the app icon. | For details, please refer to Application Icon Badges. |
Wearables and TVs do not support this notification format.
[h2]Large Notification Icon
| Description | Image Display |
|---|---|
| This format applies to notifications with image preview. | For details, please refer to Styles for Notifications with Image Previews. |
A large notification icon must meet the following requirements:
Use a JPG, JPEG, PNG, BMP, or WEBP image if possible. The total number of the image's pixel bytes must not exceed 192 KB. If it exceeds this limit, the image will not be displayed.
Avoid highly saturated or solid colors (such as black or red). Keep color saturation and brightness with a range of 10% to 90%.
Use an image that is clear and easily understandable. Avoid using elements that affect the image view experience, including but not limited to QR codes, pixelation, obvious noise, and densely arranged text and symbols.
Ensure that the image quality matches the overall notification quality. Avoid cluttered or overly complex images with multiple elements that reduce the visual appeal.
Ensure that the image does not obstruct critical notification text.
Wearables do not support this notification format.
[h2]Multi-line Text Format
This format applies when a notification contains a large amount of text that needs to be displayed in a clear, orderly layout.
| Description | Image Display |
|---|---|
| A maximum of three separate lines of content can be displayed. Excess content of each line will be truncated with an ellipsis (...). | For details, please refer to Style for Multi-line Text Notifications. |
Wearables do not support this notification format.
Notification Redirection
A notification should not be used to launch another app.
A notification should not link to an illegal website.
A notification should not induce users to download a third-party app.
Notification Switch Authorization
When your app is launched for the first time, ask the user whether to allow notifications.
Disable the notification switch by default until explicit user consent is obtained.
Other Rules
Do not tamper with, damage, or decompile functions provided by Push Kit or modify the basic functions of Push Kit.
Avoid any other behavior that may compromise user experience.
To integrate Push Kit, you are advised to set a quick entry for enabling app notifications in your app. This will allow users to easily locate the notification categorization switch, thereby enhancing their notification management experience and helping to reduce the app notification disabling rate.