Practical Guide to Publishing Flutter Apps on Chinese App Stores: Challenges, Analysis, and Recommendations
This article shares a detailed experience of publishing a Flutter‑based logistics application across major Chinese app stores, analyzes the difficulty levels and specific review issues for each platform, and provides concrete recommendations to avoid common pitfalls and streamline the submission process.
Background
The Flutter‑based logistics suite (including logistics, shipping, receiving, and driver apps) has been trialed and stabilized, and the team decided to self‑handle the app‑store submission after finding third‑party services costly and unsuitable for Flutter.
Store Submission Status Analysis
App variants: logistics, shipping, receiving, driver.
App Store
Submission Difficulty
Remarks
Apple App Store
★
All four apps can be submitted
Xiaomi App Store
★
All four apps can be submitted
Huawei App Gallery
★★★★
Only logistics app can be submitted
Tencent MyApp
★★★
Only shipping app can be submitted
Honor App Store
★★★
Only shipping app can be submitted
vivo App Store
★★★★★
—
OPPO App Store
★★★★★
—
Pitfalls and Recommendations
When the review feedback is unclear, contact the reviewer promptly; after each modification, re‑submit and be prepared for new issues, checking the whole app for similar problems.
Submit to all stores simultaneously and collect all rejection points for batch fixing to speed up the process.
Each app needs its own privacy policy and service agreement, customized according to the provided templates and actual app functionality.
Issue Collection
Huawei App Gallery
Key review problems:
Missing permission‑usage explanations for camera, location, storage, Bluetooth, contacts, etc.
Privacy policy and service agreement checks, with accuracy issues.
Occasional invalid clicks on privacy‑policy links due to fast automated checks before the backend returns the correct URL.
Thoroughly audit all used permissions and provide clear usage statements.
Tencent MyApp
Key review problems:
Inconsistent screenshots and app logo; they must match the actual app.
Functional and user‑experience issues identified during review.
Ensure all submitted assets are identical to the app.
Honor App Store
Key review problems:
Functional and user‑experience issues.
vivo App Store
Key review problems:
Functional and user‑experience issues.
Push‑notification feature lacks a disable option.
Compatibility testing failures.
OPPO App Store
Submission documentation is demanding; extensive screenshots are required to fully describe the app.
Key review problems:
Functional and user‑experience issues.
Need to provide convenient, reasonable, and effective complaint/report channels (e.g., online customer service) and note the navigation path in the supplemental description for reviewers.
Conclusion
Before submission, carefully study each store’s review policies, map app functions and permissions against them, and address the identified gaps; this can avoid about 80% of review rejections. The remaining 20%—compatibility, manual testing, and store‑specific requirements—require detailed analysis of review feedback and thorough remediation. Publishing is the final step; patience and meticulousness are essential for success.
Rare Earth Juejin Tech Community
Juejin, a tech community that helps developers grow.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.