This skill should be used when the user asks about "Play Store requirements", "Play Store review guidelines", "Play Store rejection reasons", "why was my app rejected from Google Play", "Google Play compliance", "Data Safety Section", "target SDK requirements", "Android app submission checklist", "React Native Play Store", "Expo Play Store submission", or needs guidance on Google Play Store compliance, common rejection reasons, privacy requirements, or submission readiness.
How this skill is triggered — by the user, by Claude, or both
Slash command
/google-playstore-toolkit:playstore-requirementsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Comprehensive knowledge base for ensuring Android apps (native Kotlin/Java, React Native, or Expo) meet Google Play Store policies and pass review. Google Play enforces policies through both automated scanning (pre-launch reports) and manual review, with policy violations leading to app removal, suspension, or account termination.
Comprehensive knowledge base for ensuring Android apps (native Kotlin/Java, React Native, or Expo) meet Google Play Store policies and pass review. Google Play enforces policies through both automated scanning (pre-launch reports) and manual review, with policy violations leading to app removal, suspension, or account termination.
The most frequent Google Play policy enforcement actions, ranked by frequency:
For detailed actionable checks for each category, consult references/common-rejection-reasons.md.
Every sensitive permission requires justification. Restricted permissions (SMS, call log, accessibility) require a declaration form in Play Console. Target SDK must be 34+ (Android 14). All components with intent filters must have explicit android:exported declarations.
For the complete permissions reference, consult references/android-permissions-guide.md.
All apps must complete the Data Safety Section in Play Console. Declarations must accurately reflect all data collection, sharing, and handling practices including third-party SDKs. Account deletion must be available both in-app and via web if the app supports account creation.
For Data Safety Section requirements, consult references/data-safety-requirements.md.
Google Play requires apps to target recent API levels:
All digital goods and services must use Google Play Billing Library. Physical goods and services can use alternative payment methods. Subscription apps must display pricing, renewal terms, and provide access to Google Play subscription management. Purchase acknowledgment within 3 days is mandatory.
Adaptive icons (API 26+) with foreground and background layers are required. Play Store listing requires a 512x512 high-res icon and 1024x500 feature graphic. App screenshots must accurately represent the app.
Apps must use HTTPS for all network communication. Network security configuration should block cleartext traffic. ProGuard/R8 should be enabled for release builds. WebView must not have dangerous settings like setAllowFileAccessFromFileURLs(true). Hardcoded secrets and API keys must be removed from source code.
Hermes engine should be enabled for performance. Development artifacts (Flipper, console.log, localhost URLs) must be removed from release builds. Native module permissions must be declared in AndroidManifest.xml. EAS Build production profile should use app-bundle for Play Store.
For React Native/Expo-specific guidance, consult references/react-native-expo-gotchas.md.
| File | When to Consult |
|---|---|
references/common-rejection-reasons.md | Troubleshooting a specific rejection or violation |
references/android-permissions-guide.md | Implementing or auditing permissions and declaration forms |
references/data-safety-requirements.md | Completing Play Console Data Safety Section |
references/react-native-expo-gotchas.md | React Native or Expo-specific configuration issues |
When reviewing an app for Play Store readiness:
npx claudepluginhub crgeee/google-playstore-toolkit --plugin google-playstore-toolkitAudits iOS/iPadOS/macOS app projects against App Store Review Guidelines before submission. Supports Swift/ObjC, Flutter, React Native, Expo, Kotlin Multiplatform, .NET MAUI, Cordova/Ionic, Unity.
Reviews iOS/macOS/tvOS/watchOS/visionOS app code against Apple's App Store Review Guidelines to catch rejection risks before submission.
Guides App Store submission preparation and rejection prevention. Covers privacy manifests, StoreKit/IAP rules, ATT, HIG compliance, and metadata requirements.