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

The vivo App Store is vivo's official software distribution channel. Mainland publishing uses the China-facing vivo Open Platform and its current console requirements, which differ from vivo's international system and Funtouch OS documentation.

What you need to know

Register and complete the offered individual or enterprise real-name verification.
Confirm foreign-developer eligibility for the mainland channel before scheduling a direct launch.
Prepare APP filing, software-copyright or accepted ownership evidence, and sector qualifications.
Privacy, permissions, third-party SDKs, deletion and reviewer access are substantive review items.
Test notifications, background work and compatibility on OriginOS devices.

Start with China's Android App Stores Explained if you are selecting channels.

Account and publisher choice

Create the developer account under the entity that will control the listing. Mainland enterprise verification commonly uses business registration and authorised operator information. Individual publishing, where offered, can be restricted for particular categories. A foreign company should confirm whether it can complete mainland verification and APP filing, rather than inferring eligibility from an international account.

When using a Chinese subsidiary or publisher, document IP ownership, account access, app filing, data processing, signing-key custody, support, revenue and transfer on termination. Nominee ownership is particularly risky when it leaves the foreign developer unable to update its own app.

Evidence and listing preparation

Gather the Software Copyright Registration Certificate or the alternative vivo currently accepts, APP备案 record, relevant website ICP information and category licences. Names, versions and entities should be consistent. Review software copyright registration and ICP filing as separate workstreams.

Prepare Simplified-Chinese name, summary, full description, icon, screenshots, category, privacy URL, support details and release notes. The screenshots must come from the submitted functions, not a foreign version with unavailable Google features.

APK, signing and privacy

Use a final package name, production signing certificate and increasing version code. Back up the keystore, record fingerprints and test an upgrade over the current store build. Package or signature conflicts require ownership resolution and can block normal updates.

The Chinese privacy notice should describe the controller, purposes, data, permissions, SDK recipients, retention, security, user rights, account deletion and contact. Ensure SDK collection and permission timing match the notice. vivo provides security/privacy testing capabilities; use the current platform tools before submission.

Submission steps

Register on the mainland vivo Open Platform and complete real-name verification.
Create the app with the permanent package name.
Upload the production-signed APK and verify parsed identity/version.
Add Chinese listing data, screenshots, category and privacy URL.
Upload APP filing, copyright/ownership and sector evidence.
Declare permissions and third-party SDKs accurately.
Add account deletion and working reviewer credentials.
Run security, privacy and compatibility checks.
Submit and remediate the exact reported issue.
Release, verify update delivery and monitor device/OS health.

Review time is variable rather than a reliable fixed input to the launch date. Category and evidence complexity, queue length and repeat testing all matter.

OriginOS, Funtouch OS and SDKs

OriginOS is relevant to mainland vivo devices; Funtouch OS is more common in vivo's international markets. Test the system actually used by the target customers. Cover push delivery, battery restrictions, deep links, permissions, storage/media, login, payment and upgrades.

vivo Push, account, payment, advertising and game SDKs are optional integrations. Each adds credentials, commercial terms, data flows and disclosure. They do not replace app filing or sector permission. Use an SDK inventory and remove capabilities not required by the vivo build.

Common rejection reasons

Developer, copyright, filing and app identity do not align
Package ownership or signature cannot be verified
Category licence is missing or expired
Privacy policy is inaccessible or inconsistent with traffic
Sensitive permissions are excessive or requested without context
SDK collection starts before the required choice
Account deletion or test credentials are absent
App crashes, contains security risks or relies on unreachable services
Chinese metadata and the binary describe different products

Updating an app

Preserve package and signature, increment the version code and revise all affected listing/privacy declarations. Test schema migrations and rollback. If the console offers phased rollout, begin with a monitored cohort. Approval on Huawei, Xiaomi or OPPO is not evidence of vivo approval.

Frequently asked questions

Can an international vivo account publish to mainland China?

Not necessarily. The answer depends on the account types and regions currently supported by the China-facing console.

Must every app integrate vivo Push?

No. It is a technical option, though it can improve delivery on target devices.

Are APP filing and software copyright registration the same?

No. Filing identifies the service/operator; registration is ownership evidence.

Should I test on Funtouch OS for a mainland release?

Test it if your users run it, but OriginOS should be represented for mainland-market vivo devices.

Conclusion

A maintainable vivo release comes from entity and evidence alignment, stable Android identity, transparent privacy behaviour and device-specific tests. Confirm the live mainland console at every release because qualification rules evolve.

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