Launch · 04 Editorial guide
App Filing, Domains and Digital-Service Launches in China
App filing, domain administration and telecom licensing are connected but distinct workstreams. Inventory the public product, operator, domain, host, app stores, mini-programs, SDKs and regulated functions before setting a launch sequence.
First job Inventory the app, domain, host, operator and content functions before opening separate filing workstreams.
Start here
Key considerations
The first questions are about urgency, governance and preservation — before collection expands or interviews begin.
- Which app, site, mini-program or domain will be public?
- Who is the registered and actual operator?
- Which host, store, SDK and regulated functions are involved?
Direct answer
What this page decides
02
An app launch in China requires more than an app-store submission. An app providing internet information services in China must complete the applicable MIIT filing before launch. The route also covers mini programs and quick apps through their distribution platforms. Identify the true app operator, network access provider, distribution platform, domains, IP addresses and backend services; align those records with the filing holder and any existing website filing. An existing website filing can reduce repeated identity information, but it does not automatically file a separate app. Regulated news, publishing, education, audiovisual, religious and other content can require prior sector approval. Filing also does not replace VATS licensing, cybersecurity, privacy, algorithm, software copyright, consumer or app-store requirements. After launch, the filing number must be displayed and linked, and changes or cessation must be reflected through the proper process.
At a glance
Which fact changes the next route
Use the fact that changes ownership or urgency to decide the next move.
| Question | Why it matters | Next route |
|---|---|---|
| What digital products are launching? | Native apps, mini programs, quick apps and websites can create separate records and platform workflows. | Inventory every package, platform identifier, service name and release channel. |
| Who is the app operator? | Developer, brand owner, publisher, backend operator and contracting entity may differ, but the responsible filing holder must match reality. | Map control, terms, billing, support, data and content responsibility. |
| Which network resources support it? | Domains, IP addresses, access providers and backend infrastructure are checked during filing and must satisfy domain and filing rules. | Prepare a domain, IP and hosting register tied to each app. |
| Does the service need more than filing? | Commercial telecom functions and regulated content can require licences or approvals before filing and launch. | Run the VATS and content-approval analysis in parallel. |
| Who can block distribution? | Access providers, app stores, mini-program platforms and device manufacturers must not support unfiled apps. | Build platform verification and release dependencies into the launch plan. |
Scope
What this page owns — and what it does not
Practical workflow
Action, evidence, legal gate, output
| Action | Documents / evidence | Legal gate | Output |
|---|---|---|---|
| Inventory products and release channels | Apps, package names, platform IDs, mini programs, quick apps, websites, stores and launch dates | Identify each separately filed or verified service | Digital-product register |
| Confirm operator and service perimeter | Entity chart, terms, developer and publisher accounts, billing, support, functions and revenue | Align the responsible operator and test ICP, VATS and sector approvals | Operator and permission matrix |
| Map domains and network resources | Domain ownership, registrar, real-name records, DNS, IPs, hosting, CDN and backend APIs | Match resources to operator and approved providers | Network-resource evidence pack |
| Clear content and data dependencies | Content catalogue, publishers, moderation, privacy flows, SDKs and required approvals | Complete prerequisite approvals and separate regulatory workstreams | Launch dependency tracker |
| Submit through provider or platform | Filing form, commitments, identity, existing website record, platform and access-provider verification | Resolve inconsistent names, identifiers and network resources | Accepted app filing |
| Control distribution and display | Store listing, mini-program page, in-app filing-number display and public query | Do not release before filing; make the number visible and linked | Verified launch record |
| Maintain versions and closure | Change log, new packages, operator and domain changes, platform notices and cancellation plan | File changes or cancellation when recorded facts or service status change | Current lifecycle register |
Documents
What to gather before the next call
These items help clarify the file; they are not a legal requirement list.
| Item | Why needed | Who holds it | Risk if missing |
|---|---|---|---|
| App and channel inventory | Captures every package, mini program, store and website dependency | Product and release management | One channel launches without filing |
| Operator responsibility file | Shows who controls the service and should hold the record | Corporate, legal and product | Developer or affiliate is used as a nominal holder |
| Domain and network-resource register | Links domains, IPs, backend and access providers to each product | Infrastructure and domain administrators | Verification fails or production drifts from filed data |
| Content and permission matrix | Identifies VATS licences and sector approvals beyond filing | Regulatory, content and legal | Filing is mistaken for substantive permission |
| Platform submission and result | Preserves verification, commitments, number and release evidence | Compliance and platform operations | No auditable link between filing and distributed app |
| Version and change register | Tracks identifiers, operator, resources, functions and closure | Release and compliance owners | Filed information becomes inaccurate |
Common failure points
Where files usually break
Assuming a website ICP filing automatically covers every native app, mini program or quick app.
Filing under the developer or publisher account holder when another entity operates, contracts, bills and controls the service.
Using domains, IPs or backend services whose ownership and provider records do not align with the filing application.
Treating app filing as a substitute for commercial VATS licensing or regulated-content approval.
Leaving app-store, mini-program platform and device-preinstallation verification until the release date.
Displaying the filing number only on a website rather than in the app's required prominent location and public-query link.
Changing operator, service name, domains, package identifiers or service functions without assessing filing updates.
FAQ
Narrow follow-ups owned by this page
Does an existing website filing cover a new app?
No. Existing identity information may be reused, but the app and its relevant identifiers and resources still need to be added through the app-filing process.
Are mini programs included?
The MIIT notice addresses app distribution platforms including mini programs and quick apps. The operator should follow the relevant platform's connected filing workflow.
Can an app launch while filing is pending?
A new app covered by the rules should complete filing before providing the service. Access providers, distribution platforms and device manufacturers must not support an unfiled app.
Does app filing approve privacy or content compliance?
No. Privacy, SDK governance, cybersecurity, algorithms, content and sector approvals remain separate, even when their evidence affects launch readiness.
Decision map
Keep the question bounded.
- Inventory launch surfacesList domains, sites, apps, mini-programs, app stores, APIs and customer-facing entities.
- Match operator recordsAlign registrant, sponsor, host, developer account, business licence and public disclosures.
- Open parallel workstreamsSeparate app and domain filings from ICP, VATS, content, cybersecurity and data obligations.
- Sequence releaseSet evidence-backed filing, review, testing and change-control gates before public availability.
Quick answers
Need the short version? Start with one narrow question.
These explainers answer one question. They do not replace this topic route or a deep guide.
Curated resources
Open the asset that matches this job.
China ICP Filing Guide
Practical filing route for China-hosted websites, including operator, host and launch dependencies.
China ICP, VATS & Telecom Licensing Guide
Service classification, ICP filing, VATS catalogue items, foreign-investment access and operating-route analysis.
MIIT ICP/IP/domain filing system
Official MIIT filing and public-record service for internet information and domain-related administration.
Measures for Administration of Internet Information Services
Official administrative rules distinguishing commercial licensing from non-commercial filing and addressing sector approvals, service scope, number display and operating obligations.
Measures for Record-Filing Administration of Non-Commercial Internet Information Services
Official MIIT filing rules, revised in 2024, covering territorial scope, online submission, provider verification, regulated-content approvals, number display, changes and cancellation.
MIIT Notice on Mobile Internet Application Record Filing
Official app-filing framework covering operators, apps, mini programs and quick apps, network resources, provider and platform verification, pre-launch filing, number display, changes and enforcement.
Measures for Administration of Internet Domain Names
Official MIIT rules governing domain services, registration providers, identity information, resolution, security, user rights and supervision in China.
Helpful to prepare
Facts that make the next conversation clearer.
These items are orientation aids, not a legal requirement list.
Counsel hand-off
What to bring when you instruct
Bring the full app, mini-program, quick-app and website inventory, package and platform identifiers, screenshots and store listings, proposed operator and group chart, developer and publisher accounts, functions and revenue flows, customer terms and billing, content categories and approvals, domains and registrars, real-name records, DNS, IP and backend architecture, hosting, CDN and access-provider accounts, SDK and data-flow inventory, existing ICP or VATS records, filing submissions and platform correspondence, release schedule and anticipated operator, domain, package or service changes.
Local context
Add location only when the filing or pilot route changes.
National service classification comes first; infrastructure location, filing practice and approved pilots follow.
Open city and province guidesCounsel hand-off
Need technology and telecom counsel?
This hub organises filing, catalogue and operating-route questions. It does not determine licence scope or foreign-investment access on your facts.
Find technology counselLegal review
Who reviewed this guide
Need qualified counsel?
Move carefully. Move with a record.
Use the portal to identify counsel for this practice and related China-side issues.