Blog · Google Play
How to check code before Google Play submission
Google Play's repetitive content and spam policies target developers who publish many similar Android apps. A structural Kotlin/Java audit before upload prevents costly rejection cycles.
What Google Play evaluates
Play moderation inspects APK structure, developer history, and app differentiation. Shared Gradle modules, identical Activity flows, and copy-pasted ViewModels across flavors are common rejection triggers.
Pre-submission workflow
Export your Android Studio project (or each product flavor) as ZIP. Upload to apporig alongside every other app in your Play catalog. Review COPY pairs. Rewrite shared domain layers — not just res/ assets. Rescan. Upload to Play Console only after OK or accepted RELATED status.
Gradle flavor tip
If you ship many flavors from one repo, compare each flavor export separately. Identical main/ source sets with different strings.xml are not enough differentiation.