3.1 Your atomic service must have good compatibility and be properly adapted to Huawei's mainstream devices. It must be able to launch and uninstall normally, without frequent crashes, force quits, non-responsiveness, or other malfunctions. It must not require third-party software to start or uninstall.

3.2 Your atomic service must not exhibit abnormalities in account registration or association processes, including but not limited to being unable to receive SMS verification codes or failure to use accounts. It must not enforce the input of invitation codes or referral codes as a prerequisite for registration.

3.3 Your atomic service features must be fully implemented and function right. Those with unfulfilled features may be rejected. This includes, but is not limited to, atomic services that are under testing, have incomplete development of functional modules, cannot run independently, or redirect users to third-party platforms such as mini programs or apps when their main features are accessed.

3.4 Your atomic service must provide practical value by offering practical features or services with creatives built in. It must not merely display information or provide basic features already offered by the system. (For more information, please refer to Atomic Service Review FAQs.)

3.5 Do not submit two or more severely homogenized atomic services with identical or nearly identical pages, content, or features. Additionally, avoid submitting multiple atomic services with similar content for different groups, times, sports/recreational activities, programs, species, educational stages, regions, or other scenarios. Ensure that the names, pages, content, and features of your atomic services to be submitted are distinct and irreplaceable to prevent confusion. (For more information, please refer to Atomic Service Review FAQs.)

3.6 Avoid developing new atomic services in overly saturated categories, such as electronic wooden fish apps, random selection tools, timers, calculators, flashlights, notepads, bookkeeping, weather, number format conversion, calendars, compasses, smart remote controls, mirrors, sleep aids, ID photo tools, color assistants, barrage display apps, and media players. Unless your atomic service provides a unique, high-quality experience with diverse and valuable features, it may be rejected or removed. (For more information, please refer to Atomic Service Review FAQs.)

3.7 Your atomic service must not engage in activities that harm user interests, such as excessive marketing and tricky redirections. Ensure that your atomic service features be accessible within the atomic service itself. It must not require the use of other apps or atomic services as a prerequisite, nor include malicious or unclear links redirecting outside the atomic service. This includes but is not limited to:
（1）Engage in malicious redirection, such as redirecting users to third-party services, apps, websites, or external pages with incentives like money or task-based rewards without actually providing a specific service.
（2）Induce redirections to an app or an app download page when the atomic service's basic features have not been implemented or made available.
（3）Recommend, promote, rank, or frequently redirect to other atomic services and apps, or provide assistance for such behaviors.
（4）Forcibly interrupt user access to your atomic service features or services, requiring an app redirection or download to proceed. For example, require an app redirection or download to access features or services, or to enjoy the entire service, or when the atomic service can provide the needed features.

3.8 The atomic service you are releasing must not be a debuggable version. For security reasons, turn off the debugging feature for your atomic service before its release.

3.9 Your atomic service must not provide false or misleading features, information, or claims, such as claiming to offer features (for example, mosquito repelling) that are not actually accessible.

3.10 Your atomic service must not assist users in misleading others or provide features for deceptive or illegal activities, such as generating or assisting in the creation of seals and identity information, nor promote or assist in the creation of text, images, and/or videos to spread false or misleading information.

3.11 For the pop-up feature, your atomic service must clearly state the specific form, content frequency, and cancellation channels, and prominently display the identity of the feature provider. Your atomic service must not interfere with or prevent users from closing pop-ups. The detailed requirements for Internet pop-up information are the same as those in Atomic Service Content.
（1）Your atomic service must explicitly inform users of the specific form, content frequency, and cancellation channels of the pop-up feature, through service agreements or other means.
（2）Messages pushed by your atomic service in the notification bar must be closable.
（3）Your atomic service must not push unrelated content in the notification bar.
（4）Your atomic service must clearly display the identity of the push service provider, without hiding the name and icon of the atomic service. Anonymity is not allowed.

3.12 If the main feature of your atomic service requires a payment to be activated, your atomic service must provide a free trial feature. If there are any other usage restrictions after payment, they must be clearly stated before the payment can be made.

3.13 Your atomic service must not bypass the review mechanism for automatic updates (and should use components that can be downloaded on AppGallery for updates). It must not download, install, or execute external code that may modify, replace, or update the atomic service's features or functions.

3.14 Your atomic service must support normal operation in an IPv6 network environment.

3.15 The features declared by the linkFeature attribute of an atomic service must be appropriate, complete, and usable, without impairing user experience. The requirements include but are not limited to:

(1) The features supported by the linkFeature attribute must match the actual functions or content of the atomic service.

(2) The features supported by the linkFeature attribute must belong to the atomic service itself, and must not redirect users to other atomic services, third-party apps, or external pages.

(3) The feature type declared by linkFeature must belong to the system-provided enumeration values. For details, please refer to Application Link Description.

目录