How to Publish an App on the Xiaomi App Store in China

The Xiaomi/HyperOS developer platform operates a core app-distribution channel for Xiaomi and Redmi devices in mainland China. This guide covers its China-facing workflow, whose account and evidence requirements can differ from Xiaomi's international developer console.

What you need to know

Verify the developer as an individual or enterprise using the options currently available for the app category.
Xiaomi's official ecosystem policy states that apps need accepted software-copyright evidence and must complete APP filing.
The package name, Android copyright document, developer entity and filing record must be consistent.
Privacy review covers the APK and third-party SDK behaviour, not only the policy URL.
MIUI and HyperOS compatibility, push and absent Google services require device testing.

Read China's Android App Stores Explained before deciding store coverage.

Account and entity preparation

Register on the China-facing Xiaomi/HyperOS developer platform and complete the offered real-name or enterprise verification. A mainland company generally supplies its business licence and authorised operator details. Foreign companies should confirm direct eligibility with Xiaomi before building the launch schedule. If direct verification or filing is unavailable, use a mainland subsidiary or properly contracted publisher rather than a purchased account.

Align the developer-account entity with the APP备案 operator and software-copyright claimant. When they differ, obtain an authorisation that the store accepts. Xiaomi's current qualification FAQ says its copyright and filing evidence must correspond to the app and developer information.

Prepare the binary and listing

Use the final package name from the first submission. Sign the release APK with a protected production key, increment versionCode, and record the certificate fingerprint and package hash. Test upgrades from the public build.

Prepare Simplified-Chinese name, introduction, description, icon, phone screenshots, category, support contact, privacy URL and reviewer credentials. Metadata must describe functions visible in the submitted build. Explain regional, hardware or paid-access restrictions.

Compliance material

Xiaomi's official policy lists a Computer Software Copyright Registration Certificate or accepted APP electronic-copyright certificate and APP filing. It says the Android qualification must match the published app and enterprise information. This is store policy and evidence handling; it should not be restated as a universal rule that copyright only exists after registration.

Upload any category-specific licence requested. Keep ICP and APP filing separate: APP备案 records the mobile internet service, while website ICP filing concerns a website/service and network access. See Software Copyright Registration and ICP Filing.

Privacy engineering

Publish an accessible Chinese privacy policy and reconcile it with actual traffic. Declare sensitive permissions and every third-party SDK. Delay nonessential SDK initialisation until the appropriate consent. Provide contextual permission prompts and a usable path to withdraw consent, exercise rights and delete an account.

Common failures are pre-consent identifiers, undeclared analytics or advertising SDKs, blanket storage/location requests, an unreachable policy page, or different app/operator names across the notice and console.

Submission process

Authenticate the correct developer entity on the mainland platform.
Create the app with its permanent name and package.
Upload the production-signed APK and verify parsed version/signature data.
Add Chinese metadata, screenshots, category, contact and privacy URL.
Submit copyright, APP filing and industry qualifications.
Declare permissions, SDKs and account-deletion route.
Supply stable reviewer credentials and instructions.
Run security and compatibility checks, then submit.
Address the exact rejection with a corrected package or evidence.
Verify public listing and update delivery on Xiaomi/Redmi devices.

Review time varies with category, evidence and queue. Use the console's current status rather than an unofficial fixed promise.

MIUI, HyperOS and services

Test notification delivery under battery controls, background restrictions, deep links, file/media access and upgrade behaviour. Xiaomi push can improve delivery but adds credentials, SDK lifecycle and privacy disclosure. Xiaomi billing or advertising services, when used, have separate commercial rules; they do not replace filing.

Mainland devices may not provide dependable GMS. Replace or gracefully degrade Firebase push, Google Sign-In, Maps, reCAPTCHA and Google-hosted assets. Test with a fresh mainland-market device, not only an emulator with Google services.

Common rejection reasons

Copyright, filing, app name, package or developer entity mismatch
Changed signature or conflicting package ownership
Missing sector licence or invalid document
Inaccurate screenshots or description
Sensitive permissions without an evident user feature
SDK collection before consent or missing SDK disclosure
No account deletion or no usable test account
Crash, empty screen, malware finding or unreachable dependency

Updates and phased releases

Use the same package and signing key, increase the version code and update listing/privacy evidence when behaviour changes. If phased release is offered for the submission, monitor crash, login, push and payment signals before expanding. Maintain a separate approval record for Xiaomi even when the same binary is in other stores.

Frequently asked questions

Can I reuse my international Xiaomi developer account?

Not necessarily. Eligibility depends on mainland authentication, distribution-region support and the filing fields available in the current China-facing platform.

Is an APK signature important for later updates?

Yes. Android upgrade trust depends on package and signature continuity.

Does Xiaomi require software copyright evidence?

Its published ecosystem policy says accepted copyright evidence is required for app release. Check the current category FAQ for permitted documents.

Is Xiaomi push legally required?

No. It is a technical option; if used, disclose and govern it like any other SDK.

Conclusion

The shortest path is to align the China-facing account, filing and Android rights evidence before uploading. Then validate privacy behaviour and Xiaomi-device compatibility using the same release controls you will maintain after launch.

This article is for general informational purposes and is not legal, tax, accounting, or regulatory advice.