China's Android App Stores Explained: A 2026 Distribution Guide

If you maintain an Android app outside China, mainland distribution is not a matter of adding one more country in Google Play. Google Play is generally not the default discovery or update channel on mainland-market phones. Users instead obtain apps from handset-maker stores and large third-party stores. This guide is for engineering and product teams deciding whether to operate that portfolio themselves or through a mainland publisher.

What you need to know

There is no single submission that publishes to every important mainland Android store.
Huawei, Xiaomi, OPPO and vivo operate stores integrated with their devices; Tencent MyApp (应用宝) is a major third-party channel.
Each store has its own developer verification, listing, binary and review record.
MIIT mobile-app filing (APP备案), website ICP filing, a commercial ICP licence and Software Copyright Registration are separate things.
A foreign developer may be able to create some global platform accounts, but mainland distribution, filing and category qualifications commonly require a mainland entity or an appropriately authorised publisher.
Budget for repeated review, device testing, metadata updates, privacy audits and multiple release dashboards.

How the ecosystem differs from Google Play

Mainland Android is fragmented by distribution, services and device software. Manufacturer stores are preinstalled, trusted by the operating system and positioned to deliver updates. Tencent MyApp reaches users across device brands. Samsung Galaxy Store can matter for Samsung users, but it is not a substitute for the leading domestic channels.

Market position varies by device installed base, audience and measurement method, so no single public ranking remains definitive. Store coverage is best guided by your own device analytics and acquisition data.

Store	Type	Best reason to include it	Operational note
Huawei AppGallery	Manufacturer	Huawei and HarmonyOS ecosystem	Global and mainland operations must be checked separately
Tencent MyApp (应用宝)	Third-party	Broad Android reach and Tencent integrations	China-facing verification and Chinese metadata are central
Xiaomi App Store	Manufacturer	Xiaomi and Redmi users	MIUI/HyperOS compatibility and Xiaomi policy matter
OPPO App Market	Manufacturer	OPPO and ColorOS users	China and global portals can have different access rules
vivo App Store	Manufacturer	vivo and OriginOS users	Its international workflow may not cover mainland China
Samsung Galaxy Store	Manufacturer	Selected Samsung segments	Assess its incremental reach for your audience

One upload does not propagate across this table. Even when a distributor performs submissions for you, it is operating several store accounts and reviews behind the scenes.

Four documents people often confuse

Mobile-app filing

MIIT's app filing is commonly called APP备案. MIIT's 2023 notice says app operators providing internet information services in China must file, and distribution platforms must not distribute unfiled apps. The filing records the operator, service, domains, IP resources and related information. A filing number must be displayed prominently in the app and linked to the MIIT system.

Website ICP filing

ICP备案 is the filing used for non-commercial internet information services hosted in mainland China. It is tied to the service operator, domains and access provider. See ICP Filing for Foreign Developers before choosing infrastructure.

Commercial ICP licence

An ICP许可证 is a licence for qualifying commercial internet information services. It is not the number placed in a website footer after ordinary filing. Whether your business needs a licence depends on the service and corporate structure; confirm with the relevant provincial communications administration.

Software Copyright Registration

Computer Software Copyright Registration (计算机软件著作权登记) produces evidence about a registered software work and claimant. It is not the source of copyright and does not itself authorise a regulated business. Mainland Android stores commonly request the certificate or accepted alternative ownership evidence. Read Do You Need Software Copyright Registration for a Chinese App?.

Prerequisites before opening store consoles

Choose the publishing principal first. The developer-account owner, app-filing operator, copyright claimant, privacy-policy controller and merchant should tell a coherent story. If they differ, prepare written licences and authorisations.

A typical submission pack includes:

business registration and identity documents for account verification;
a mainland contact and phone number where the platform requires them;
app filing information and any website ICP information requested;
software-copyright certificate or alternative ownership evidence;
sector permits for categories such as games, news, publishing, finance, maps, healthcare or audiovisual content;
Chinese app name, short and long descriptions, icon, screenshots and update notes;
a public Chinese privacy policy, user agreement and support contact;
a production-signed APK, package name, version code and signing-certificate fingerprint;
reviewer credentials and instructions for gated functionality.

Store policy changes faster than this list. Recheck the console's current qualification matrix immediately before submission.

Build for mainland devices

Keep one package name and signing lineage per app unless a documented channel strategy requires otherwise. Losing the production keystore or changing the signature can make an update look like a different app. Maintain monotonically increasing version codes and keep a release ledger by store.

Audit every runtime permission and every bundled SDK. The privacy policy should identify the controller, purposes, data types, retention, sharing, user-rights channels and account-deletion route. The first-run consent flow should not initialise non-essential collection before the required choice. Store reviewers inspect SDK behaviour, not only your own code.

Google Mobile Services may be absent or unreliable on mainland-market devices. Test replacements for Firebase Cloud Messaging, Google Sign-In, Maps, reCAPTCHA, Google-hosted fonts and analytics. Manufacturer push services can improve delivery but introduce separate SDK credentials, privacy disclosures and release work. The same applies to Huawei Account, Xiaomi services, OPPO/vivo accounts, billing and advertising kits.

Step-by-step distribution process

Decide scope. Rank stores using your current Chinese device mix, not an unsupported market-share graphic.
Choose the operator. Use your mainland subsidiary, a properly contracted publisher or a distributor with explicit account and IP terms.
Map regulated features. Identify payments, user-generated content, media, AI, maps, healthcare, finance and games before filing.
Align ownership. Resolve differences among copyright, developer, filing, domain and merchant entities.
Complete filing and qualifications. Treat ICP filing and app filing as separate requirements.
Prepare the China build. Remove unreachable dependencies, implement compliant consent and deletion, and test domestic push/login/payment paths.
Register each console. Complete real-name or enterprise verification on every platform.
Create listings. Use accurate Simplified Chinese metadata and screenshots from the submitted build.
Submit binaries and evidence. Give test accounts, special hardware instructions and explanations of sensitive permissions.
Respond per store. A fix accepted by one reviewer is not automatic approval elsewhere.
Release in waves. Use staged release features where available and monitor crashes, login, push and payments by device brand.
Maintain records. Update listings, SDK disclosures, filings and sector permits when the product or operator changes.

Common rejection patterns

Rejections frequently follow from an app name that differs across the binary, filing and certificate; a signature that does not match the existing listing; unexplained sensitive permissions; SDK collection before consent; an inaccessible privacy-policy URL; missing account deletion; screenshots that promise unavailable features; no test account; or missing category-specific qualifications. Malware, dynamic code loading intended to bypass review, forced updates from another store and misleading download prompts create higher-risk outcomes.

Can foreign developers publish directly?

The answer depends on the platform, entity and service. Registration with an international developer programme does not by itself establish eligibility for a mainland channel or MIIT filing. In practice, foreign developers commonly use one of four routes:

Route	Appropriate when	Main risk
Direct foreign account	The platform expressly supports the entity and mainland region	Filing or qualification fields may still require a China-side operator
Mainland subsidiary	China is a durable market	Setup, governance, tax and continuing compliance workload
Licensed local publisher	A partner genuinely operates and supports the service	IP, data, revenue and exit terms must be precise
Enterprise distribution	App is only for a controlled workforce or customers	Not a route for avoiding public-store rules

Borrowed company identities and informal nominee ownership create serious continuity risks. Any arrangement involving core IP should define ownership, updates, source access, account control, data roles and termination in writing.

Strategy by product type

Small foreign developer: validate demand with iOS, web or a Mini Program where appropriate; add Android stores through a vetted publisher only after unit economics are clear.
Company with a Chinese entity: operate the principal manufacturer stores plus MyApp, using one release checklist and accountable owner.
Game: treat game approval, ISBN/approval number, publisher relationships and store revenue-share integration as a separate project.
Enterprise app: use managed, private or authenticated customer distribution where permitted; a nonfunctional public shell is unlikely to provide a viable route.
Existing-customer app: consider a web app, WeChat Mini Program, private distribution or direct customer deployment after reviewing security and platform rules.

Frequently asked questions

Is Google Play completely unavailable in mainland China?

The practical point is that it is generally not the main dependable distribution channel for mainland-market Android devices. Build your plan around the stores your users can actually access.

Does Huawei AppGallery publish to Xiaomi, OPPO and vivo?

No. Each store is a separate channel. Start with Huawei, Tencent MyApp, Xiaomi, OPPO and vivo.

Is software copyright registration legally mandatory for every app?

Not as a universal condition of copyright ownership. A store can still require registration evidence as its distribution policy.

Can one APK be used everywhere?

Often the core binary can be shared, but service SDKs, package channels and billing terms may require variants. Keep behaviour and signing controlled.

Conclusion

Begin with an entity-and-evidence map, not five console registrations. Once the operator, filing, IP and regulated features align, choose the smallest store portfolio that reaches your users and run it as a continuing release operation.

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