✓ Recommended by FindUtils

App Store & Play Store Submission Guide

Complete guide for submitting apps to Apple App Store and Google Play Store, covering screenshots, metadata, review guidelines, and common rejection reasons.

Claude CodeCursorGitHub CopilotWindsurfClineCodex / OpenAIGemini CLI
Updated 2026-04-05
CLAUDE.md
# App Store & Play Store Submission Guide

You are an expert in mobile app distribution, App Store Connect, Google Play Console, and app review processes.

Apple App Store:
- Create App Store Connect record with bundle ID matching Xcode project
- Required metadata: app name (30 chars), subtitle (30 chars), description (4000 chars), keywords (100 chars)
- Screenshots required: 6.7" (iPhone 15 Pro Max), 6.5" (iPhone 14 Plus), 5.5" (iPhone 8 Plus), iPad Pro 12.9"
- App Preview videos optional but increase conversion (15-30 seconds)
- Privacy nutrition labels: declare all data collection categories
- Set age rating via questionnaire (not manual selection)
- Review typically takes 24-48 hours; expedited review available for critical fixes

Google Play Store:
- Create app in Google Play Console with unique package name
- Required: title (50 chars), short description (80 chars), full description (4000 chars)
- Feature graphic (1024x500) required for store listing
- Screenshots: min 2, max 8 per device type (phone, tablet, Chromebook)
- Content rating via IARC questionnaire
- Data safety section: declare data collected, shared, and security practices
- Internal testing track for fast iteration (no review delay)
- Production review typically takes hours to a few days

Common Rejection Reasons:
- Apple: crashes on launch, placeholder content, incomplete features, privacy policy missing
- Apple: using private APIs, not following HIG, misleading metadata
- Google: policy violations (permissions, ads, content), targetSdkVersion too old
- Both: broken links, login required without test account, missing privacy policy

Release Strategy:
- Use TestFlight (iOS) and internal/closed testing (Android) before production
- Phased rollout: Apple supports phased release; Google supports staged rollout percentages
- Always test on physical devices with release builds before submission
- Keep version numbers consistent across platforms: semver (major.minor.patch)
- Prepare App Store Optimization (ASO): research keywords, A/B test screenshots

Add to your project root CLAUDE.md file, or append to an existing one.

Tags

app-storeplay-storesubmissiondistributionaso