ICP, APP Filing, and a Game ISBN Are Three Different Questions

ICP filing, APP filing, and the approval often called a game ISBN answer three different questions. One release may touch all three. You still need to track three records, three scopes, and often three workflows.

This is an editorial guide to asking better questions, not a determination of scope. Verify the current official process for the service, platform, entities, and game you intend to operate.

Put each acronym on the service it covers

MIIT’s notice on mobile internet application filing establishes a filing workstream for mobile internet applications and assigns responsibilities across app sponsors, network-access providers, distribution platforms, and relevant authorities. For a game team, the important signal is not a form number. It is that the application itself is a regulated service surface with an identifiable sponsor and records that platforms may verify.

ICP is commonly encountered in connection with internet information services and domains. APP filing addresses mobile applications. Game publication approval addresses the publication and operation route for the game. Apple’s current App Store Connect documentation reinforces the separation on the platform side: it discusses ICP filing information and matching metadata, then separately requires a game approval number and supporting documents for games.

Write down three questions:

1. What internet service or domain is being operated, by which entity, under which filing or license position?
2. What mobile application is being offered, by which sponsor, and how is its APP filing verified by the distribution platform?
3. What game publication and operating arrangement is approved, for which title, applicant/operator, platform, and build scope?

Give each record its own release-tracker row

Put these questions on separate rows in the release tracker. For each row record the responsible Chinese entity, official name and identifier, service or app it covers, source system, required documents, partner owner, studio owner, platform field, status evidence, and current blocker.

Draw the product surfaces too. A marketing website, account site, support portal, mobile client, PC client, backend service, and community page are not automatically covered by the same record. The diagram lets a qualified partner or adviser correct the scope without guessing what the team means by “our app.”

When reviewing a proposal, ask the partner to demonstrate the relationship among the records. Which names must match? Which account displays the information? Which document is uploaded to which platform? Who handles a correction? What happens when the app name, operator, domain, package, or build changes?

Keep the rest of the route visible

The MIIT notice covers one part of the route. An APP filing gives no proof of NPPA game approval. An ICP filing number cannot be assumed to cover every mobile app or game. Game approval leaves platform metadata, app filing, website records, SDKs, payments, data flows, minor-protection systems, and support operations to be completed.

Nor does any of these records prove player demand. Formal mainland distribution and Chinese-language visibility on an international storefront remain different routes even when they share a title and translation.

Review the notice against your actual system map

Read MIIT’s notice on mobile internet application filing beside the current platform instructions and NPPA materials for your game. Ask a qualified partner to annotate your real system and entity diagram. You should leave the review knowing which service each record covers, who owns the work, and which gaps remain.