3. App Functions

To provide optimal user experience, your app must offer expected functions and features at minimum, including normal, complete, stable, smooth, practical, and appealing functions, in accordance with good practices in the app market. You must ensure that:

3.1 Your app has good overall compatibility, works properly on mainstream Huawei devices, and can be installed, started, and uninstalled properly. Furthermore, your app does not frequently crash, unexpectedly exit, fail to respond, or encounter function failures when running, and can be easily uninstalled without the need for third-party apps.

3.2 Your app does not encounter exceptions during registration and sign-in, including but not limited to failure to receive SMS verification codes and unable to access accounts.

3.3 Your app's listed functions should be available, and can be used as normal. Apps with incomplete functions may be rejected, including but not limited to apps that are only for testing purposes, have incomplete functional modules, cannot run independently, or redirect users to third-party platforms such as mini programs or apps when their main features are accessed.

Example 1:

​

Example 2:

​

Example 3:

​

Example 4:

​

3.4 Your app should not provide the debugging function for users. For security purposes, make sure that the debugging function has been disabled before submitting the app for release.

3.5 Your app should not feature fake or misleading functions, or display or claim any fake or misleading information, for example, claiming to provide a function that is impossible to implement (example: an app that claims it can help repel mosquitoes).

Example:

​

3.6 Your app should not assist users in misleading others, for example, generating or helping generate seals or identity information, or publicize or assist users in generating text, images, and/or videos that contain misleading information.

Example:

​

3.7 If your app displays push messages, it should explicitly specify the form and frequency of push messages, and how to stop receiving such messages, and should clearly display the service provider of the push service. Your app should not interfere with or affect users when they close push messages. For details about the requirements on push messages, please refer to 4. App Content. Make sure that:
1) Your app clearly notifies users of the form and frequency of push messages, and how to stop receiving such messages in your service agreement or via another method.
2) Push messages from your app can be disabled by the user.
3) Your app does not push content that is irrelevant to its functions.
4) Your app clearly displays the service provider of the push service, and does not hide the name or the icon of the app.

Example 1:

​

Example 2:

​

3.8 If your app's main functions can only be unlocked by payment, your app provides users with free trials for these functions. If other usage restrictions still exist after users have made a purchase, your app must clearly state these before payment is made.

Example:

​

3.9 Your app does not automatically update before being reviewed (components performing app updates provided by AppGallery must be used), and does not download, install, or execute code that may modify, replace, or update app features or functions from other sources.

Example:

​

3.10 Your app should be fully functional on IPv6 networks.