A real launch, including the part that went wrong.
One client, published in detail: a US English-learning curriculum with users in several countries and no Chinese presence at all. Six Android stores live, both filings completed, App Store China in review — and one version update that came back rejected.
Published with the client’s agreement. Version numbers and store states are as at 4 October 2026.
Yakety Yak — an ESL curriculum, live in six Chinese Android stores.
- App filingFiled
- ICP filingFiled
- App Store · iOSIn review
Starting point
A US English-learning curriculum with users in several countries, and a China problem that is the usual one: no Chinese entity, no filings, no route into any Chinese Android store, and an iOS listing that could not be submitted for mainland China because it depended on Google services.
What we handled
- Chinese entity coordination — the client’s own company, never ours
- ICP website filing, then the public security filing inside the 30-day window
- MIIT app filing for the app itself
- Developer accounts across six major Android stores
- China-readiness review: privacy declaration, permission set, account deletion, third-party SDK list
- Submission to all six stores, each tracked as its own review queue
- Review remediation, including one version-update rejection (Case 02 below)
A version update bounced by OPPO — and why that was not a failed launch.
- A first listing rejected means the app is not in the store at all.
- A version update rejected means the app is live, and the store is holding back the newest build.
- “Live” is not the same as “latest version live.” Both can be true at once, and the version number is the only honest way to describe it.
The OPPO notice the client received said the submission had not passed review. That notice was about the latest version’s update — the previous build was already live and stayed live throughout.
What we did
- Read the rejection against the specific clause it cited, rather than guessing at it
- Mapped the cited issue to the exact artefact in the submission package
- Rebuilt that part of the package, and reviewed the rest of the update against the same clause
- Resubmitted, tracked the review, and cleared it
This is the least glamorous and most useful part of the work. Six stores means six reviewers reading six slightly different rulebooks, and the store that rejects you is rarely the one you were worried about.
Don’t take our word for it — open the store listings yourself.
The links below go to public pages for the app in Case 01. No login, no NDA, nothing we can edit. You can check the version number and the filing number against everything else on this page.
雅克快速英文 com.learningtogether
Published under the client’s own Chinese entity — not ours.
What those pages do prove
- The version number — 1.0.7, the same one this page claims
- The developer entity — a real Chinese company, and not us
- The app filing number, printed on the listing, which means the MIIT filing is real
- The category — a live product listing rather than a placeholder
What they do not prove
- How long the filings took — that is the ten phases →
- Which submissions were rejected first — that is Case 02 above
- Whether your category is viable in China — that is what the free check is for
The listings are in Chinese. If you cannot read them, the two things worth finding are numerals and both sit on the first screen of the Tencent MyApp page: the version number, and the filing number underneath the developer name.
We do not publish anything a client has not agreed to.
What you will never see here
- Mockups presented as screenshots
- A store name in a logo wall for a client who never went live on it
- A version number rounded up, or a “live” that means “submitted”
- Client names, logos or dashboards without written permission
What we show instead
- Version numbers, because they are checkable in the store
- The store list, with each store’s state stated separately
- The rejections, because they are where the work actually is
- The filing structure — which of the four were needed, in which order
Your launch will not look exactly like this one. Categories differ, the six stores differ in what they ask for, and the iOS route has requirements the Android route does not. The structure of the work is the same, and that is what this page is here to show.
Your launch will have its own version of Case 02.
The point of a case study is not that it went smoothly — it is that the problems were ours to fix. Tell us what you have and we will tell you where yours are likely to be.
Prefer to talk it through? Message us on WhatsApp — usually answered the same day.