How Long Does App Store Submission Take? Filing, Copyright and Review Timelines

Most companies read “how long does app store submission take” as the one or two days spent in review. In practice, finishing the code is only the starting line. Four gates follow: software copyright registration, app filing with the telecom authority, privacy compliance remediation, and parallel submission across multiple stores. Two of those gates are measured in months. If a project plan leaves them out, the result is predictable: the features shipped weeks ago, the app still is not public, and the final payment is stuck on a milestone called “launch.”

1. Submission is a compliance chain, not an upload

To publish in Chinese app stores you need four things at once: verifiable ownership of the software, a completed app filing, compliant privacy policy and permission handling, and any category-specific licences the stores require. These are checked by different authorities and none substitutes for another. “Ship first, fix paperwork later” does not work. Apple reviews mainly for privacy and functional completeness and does not insist on a copyright certificate, but it will ask for proof of ownership when an infringement complaint or account dispute arises.

2. Paperwork that runs in months: copyright and filing

A computer software copyright registration certificate is a hard requirement for corporate developers on the major Android stores. From our experience, routine registration takes one to two months, and expedited handling is available at extra cost. Expediting shortens the queue, not the correction cycle if the materials are wrong. Three details cause most rejections: the copyright holder must be the operating company, not an individual; the software name must match the final app name and the filing name exactly; and the source code excerpt and user manual, including real screenshots, must correspond to the actual features.

App filing has been a precondition for listing since 2023; stores will not publish an app without a filing number. Industry experience puts the wait at three to six weeks from submission to issuance, with noticeable regional differences. Once filed, changing core information such as package name, signature or entity means starting over, so verify the package name and signing fingerprint before you submit, not after.

Both items are calendar time, not labour hours. No amount of developer effort compresses them; the only real lever is starting early. A sensible trigger is when development passes the halfway mark and the app name and package name are fixed. Do not wait for the test release.

3. Store review: how much the channels differ

The review queue itself is usually quick. Huawei's published review guide states that routine app review typically completes within 24 hours. Apple's long-standing reference is that about half of submissions are reviewed within 24 hours and ninety percent within 48, though peaks and new-account submissions stretch noticeably. Google Play is more cautious with new accounts and sensitive permissions; budget a week or more for a first submission.

Parallel submission has a real cost. Huawei, Xiaomi, OPPO, vivo, Tencent MyApp and others each require a separate corporate developer account, separate materials and separate uploads. Account verification alone takes one to three days, and screenshot sizes, tagline limits and category rules differ per store. Listing on seven channels is effectively seven small submission projects; three to five working days for submission and remediation is a reasonable allowance.

4. Six rejection causes you can pre-empt

• Non-compliant privacy prompt: the first launch must show the privacy policy and user agreement, with “agree” and “disagree” equally prominent, and no device identifier or clipboard access before consent. Cross-platform frameworks initialise components by default, which is where this breaks.
• No test account: if the app opens on a login screen, the reviewer needs credentials in the review notes, or the submission is rejected as untestable.
• Name mismatch: app name, copyright name and filing name must match exactly; a missing character or a different suffix is enough to fail.
• Undisclosed third-party SDKs: push, maps, analytics and social login SDKs must each be named in the privacy policy with purpose and data types collected.
• Missing account deletion: the deletion flow must actually work and must not impose unreasonable hurdles.
• Missing category licence: finance, medical, education, live streaming and games require prior approval; without it the category cannot be opened at all.

5. Turning launch into something you can schedule

Build a dated checklist and run it in parallel with development. Fix the app name, package name and legal entity at kickoff and start copyright registration the same week. Start filing once development passes halfway. During test release, finish the privacy policy and SDK list, prepare screenshots and store assets, and register developer accounts. Submit the first batch of channels as testing closes, and reserve a week for rejections and fixes.

One contract detail is easy to overlook: define what “launch” means. Is it passing review on the first store, or on every store you listed? The second can be two to three weeks later than the first. Final payment milestones and the warranty start date both hang on that definition, and leaving it vague is how disputes start.

So how long does app submission take? Realistically, somewhere between three and six months, and the variable is when you started the paperwork. Treat copyright and filing as parallel workstreams rather than closing tasks, and the launch date becomes a line in the plan instead of a matter of luck.