How to Publish an App on Tencent MyApp (应用宝)

Tencent MyApp, or 应用宝, is a major third-party Android distribution channel in mainland China. Unlike a manufacturer store, it can reach users across handset brands. This guide is for foreign product teams preparing a public consumer release; it does not assume that a global Tencent login is sufficient for mainland publishing.

What you need to know

• MyApp is one channel, not a gateway to Huawei, Xiaomi, OPPO and vivo.
• Expect real-name or enterprise verification and China-facing evidence.
• APP filing, software-copyright evidence and category qualifications may be reviewed independently.
• The APK, listing, privacy notice, SDK behaviour and reviewer account must agree.
• Foreign entities should confirm current console eligibility before planning a direct release; a mainland entity or authorised publisher is common in practice.

See China's Android App Stores Explained for channel strategy.

Decide who will be the publisher

The Tencent developer account should belong to the entity responsible for the listing. A mainland enterprise account normally uses its business licence, unified social credit information, legal representative or authorised operator data, contact details and platform verification. Individual options, when available for the category, use personal real-name verification.

Foreign companies should ask Tencent support two precise questions: can this legal entity complete authentication on the China-facing console, and can it be the APP备案 operator for this service? A positive answer to the first does not decide the second. If using a publisher, document ownership, account access, filing roles, data processing, revenue, support, update rights and exit assistance.

Prepare the evidence pack

Common materials include the verified company documents, operator authorisation, Software Copyright Registration Certificate or accepted alternative rights evidence, APP filing record, relevant website ICP information and sector licences. The exact package varies by category and current policy.

The copyright document should match the software name, version and claimant story. If the developer account is not the claimant, supply an authorisation or distribution licence the platform accepts. Review the deeper ownership issues in Software Copyright Registration for a Chinese App.

Prepare the APK

Use a production APK with a stable Java-style package name, increasing versionCode and controlled signing certificate. Record SHA fingerprints and back up the keystore securely. An update signed differently from the installed app cannot be treated as a normal upgrade.

Remove debug endpoints, test payment keys, unused permissions and unintended dynamic-download behaviour. Test install, launch, upgrade, logout and deletion on representative mainland devices. If a feature needs a specific SIM, location, accessory or enterprise account, explain it in review notes.

Listing and privacy material

Provide a Chinese name, concise description, full description, category, icon, screenshots and update notes that match the binary. Claims such as “official” or “number one” need a defensible basis. Keep the privacy policy on a stable HTTPS page accessible in mainland China without login.

Build a data inventory for every SDK. Disclose provider, SDK name, purpose, information accessed, permissions and policy link where requested. Ensure optional SDKs do not collect before the appropriate consent. Explain each sensitive permission in product language, request it contextually and allow the app to work without nonessential access.

Provide an in-app account-deletion path when users can create accounts. A support email alone may not satisfy the current rule or reviewer expectation. Deletion should cover pending subscriptions, wallet balances and statutory retention clearly.

Submission workflow

1. Register on Tencent Open Platform and select the China-facing application service.
2. Complete real-name or enterprise verification with current documents.
3. Create the app using the final package name and production identity.
4. Upload the signed production APK and confirm parsed name, version and signature.
5. Enter Simplified-Chinese metadata, screenshots, icon, category and privacy URL.
6. Upload copyright, APP filing and category evidence requested by the console.
7. Declare permissions and third-party SDKs accurately.
8. Add a test account, verification-code workaround and step-by-step notes.
9. Submit for automated security and policy checks followed by the applicable review.
10. Fix the stated issue, document the change and resubmit with all functions visible to review.

What reviewers examine

Expect installation and malware scanning; signature and package consistency; broken or placeholder functions; content legality; user-generated content controls; excessive permissions; privacy-policy consistency; SDK collection; advertising behaviour; payment routes; qualifications; and whether reviewers can access all features.

Tencent ecosystem integrations such as QQ login, Tencent push, advertising or payment services are technical products with their own agreements and privacy disclosures. They are not prerequisites for every listing and do not replace filing or licences. Games follow separate publishing, approval and commercial processes.

Common rejection reasons

• App name, package, filing or copyright evidence does not match.
• The privacy policy is unavailable, generic, or omits an SDK.
• Collection starts before consent or permissions are not necessary for the stated function.
• Login requires an unreachable foreign SMS provider or no test credentials are supplied.
• The app crashes, shows empty pages or depends on unavailable Google services.
• Screenshots or description differ from the submitted version.
• Account deletion is missing or cannot be completed.
• A regulated category lacks current qualification evidence.
• Malware, obfuscated downloads or misleading advertising are detected.

Publishing updates

Keep the same package name and signing certificate. Increase the version code, update release notes and resubmit changed privacy or qualification information. Test an upgrade over the current public version, including database migration and push-token continuity. Monitor crashes and authentication by Android version and manufacturer.

Use a release matrix rather than assuming approval elsewhere means MyApp approval:

Foreign-developer alternatives

A foreign developer that cannot complete direct verification can create a mainland subsidiary, appoint a genuine publisher, launch a web or WeChat Mini Program version first, or limit distribution to a controlled enterprise audience where a lawful private route exists. Pre-verified accounts carry identity, IP and update-control problems that can make the app impossible to maintain.

Frequently asked questions

Can I use a foreign Tencent account to publish directly?

Not necessarily. The current China-facing console must support both the legal entity's authentication and its mainland app-filing role.

Does MyApp distribute to handset-maker stores?

No. Submit separately to the Huawei, Xiaomi, OPPO and vivo stores you need.

Is a fixed review period guaranteed?

No. Tencent's current dashboard and support response are the authoritative status for a submission.

Can a Tencent SDK satisfy privacy compliance automatically?

No. You remain responsible for accurate disclosure, consent sequencing, minimisation and user rights.

Conclusion

The efficient route is to align the entity, filing and rights evidence before touching the listing. Then submit a production-realistic APK with a transparent privacy flow and a reviewer account that works in China.

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

Sources and official documentation

• Tencent Open Platform
• MIIT mobile-app filing notice
• MIIT app-filing explanation
• MIIT guidance on improving mobile-app services