How to Publish an App on the OPPO App Market in China

OPPO Software Store and its Open Platform form a manufacturer distribution channel integrated with OPPO and ColorOS devices. The platform also exposes account, push, advertising and game services, but those integrations are separate from the right to publish. Documentation and account access can differ between OPPO's global and China-facing platforms.

What you need to know

Complete the China-facing developer certification available to your individual or enterprise account.
Public apps generally need APP filing; OPPO's official upload guidance says unfiled apps, apart from applicable offline exceptions, cannot be listed.
Prepare copyright/ownership and sector evidence requested for the app.
Privacy automation and manual review examine policy accessibility, consent, permissions and SDK behaviour.
Package name and signing continuity are essential for updates.

See the Android store overview for channel strategy.

Publisher and account setup

Use the OPPO Open Platform's current developer-certification flow. Mainland enterprise verification typically involves the business licence, responsible/authorised person and current contact information; individual eligibility can be limited by category. Foreign developers should obtain written confirmation of China-channel eligibility. If a local publisher is required, keep IP, account, package, signing, filing, revenue, support and exit responsibilities in the agreement.

Prepare the Software Copyright Registration Certificate or accepted ownership evidence, APP filing record, applicable ICP information and sector qualifications. The app, filing operator, developer identity and rights chain should match or be connected by accepted authorisation.

Binary and product page

Create the app only when the permanent package name is known. OPPO's upload guide says the package is the unique identifier and cannot simply be changed after submission. Upload the required 64-bit or compatible APK option displayed by the console. Protect the signing key and increment version codes.

Add an accurate Chinese name, brief introduction, full description, icon, screenshots, category, age information and contact. OPPO's guidance specifies detailed asset constraints that can change; follow the live form rather than copying old pixel limits.

Privacy and security checks

Host the Chinese privacy policy as an accessible HTML page, without login or a second redirect. OPPO's official reviewer FAQ explains that automated analysis may fail on PDFs, image documents, private cloud notes or inaccessible pages. Cover controller identity, data purposes, SDK recipients, retention, user rights, deletion and contact.

Test that no nonessential identifier or SDK collection begins before the relevant choice. Explain permissions in context. Add a working account-deletion route. OPPO provides privacy and security self-checking services; run them before review and retain the report as release evidence.

Submission workflow

Authenticate the appropriate OPPO China developer account.
Create the app with final package name and app name.
Upload the signed APK variant required by the console.
Add Chinese metadata, screenshots, category and release settings.
Provide APP filing, ownership and special-industry qualifications.
Declare permissions, SDKs, privacy URL and deletion route.
Put reviewer accounts and special configuration in review notes.
Run security/privacy and ColorOS compatibility checks.
Submit and respond to the specific evidence or binary finding.
Choose immediate or scheduled release and verify the public build.

Review time is not universal. The official community FAQ offers indicative processing for ordinary queues, while complexity, holidays, category and resubmission can change the result.

ColorOS and platform services

Test background work, notifications, deep links, media/storage access, folding screens and 64-bit compatibility. OPPO push can improve notification delivery on ColorOS. OPPO account, payment, wallet, advertising and game services are optional products with separate agreements and disclosures. None substitutes for APP filing or a regulated-sector licence.

Common rejection reasons

Missing or mismatched APP filing, rights or category evidence
Package already claimed, wrong signature or version conflict
Privacy URL cannot be parsed or omits observed SDK collection
Collection before consent or excessive permissions
Missing account deletion or reviewer access
Screenshots, description and actual features differ
Crashes, malware findings, hidden remote functionality or misleading ads
Public-expression features lacking the specific security/sector evidence requested

Updates

Use the original package and signature. Test upgrading from the store version, update privacy/SDK declarations and attach changed qualifications. OPPO offers phased publishing features; when available, begin conservatively and watch crash, login, push and transaction health before expansion.

Frequently asked questions

Is the global OPPO developer account enough?

Not necessarily. Verify China-facing certification and distribution access for the exact account.

Can an unfiled online app be listed?

OPPO's current upload guidance says public online apps should have APP filing; check the live qualification rules for narrow offline cases.

Does OPPO accept a PDF privacy policy?

Its reviewer guidance recommends an accessible static HTML page because automated analysis may not process PDF or image formats correctly.

Is ColorOS testing separate from Android testing?

It is part of Android quality work but needs device-specific coverage for background, notification and compatibility behaviour.

Conclusion

Prepare OPPO as a continuing manufacturer channel: stable package/signing, China-valid evidence, inspectable privacy behaviour and ColorOS acceptance tests. That makes review fixes and later updates predictable.

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