Play Store Submission
Complete guide to submitting your Android app to the Google Play Store.
Prerequisites
- Google Play Developer Account ($25 one-time fee)
- App built with EAS Build
- App icons and screenshots ready
- Privacy policy URL
Step 1: Create Developer Account
- Go to Google Play Console
- Pay $25 registration fee
- Accept Developer Distribution Agreement
- Complete account details
Step 2: Create App
- Click "Create app" in Play Console
- Fill in app details:
- App name: Your app name
- Default language: English (US)
- App or game: Choose appropriate type
- Free or paid: Select pricing model
- Accept declarations
Step 3: Store Listing
App Details
- App name: Up to 50 characters
- Short description: Up to 80 characters
- Full description: Up to 4000 characters
typescript
Short description example:
Fast, secure task manager with offline support
Full description example:
Take control of your tasks with our beautiful, intuitive task manager.
Features:
• Create and organize tasks effortlessly
• Set reminders and due dates
• Work offline, sync when connected
• Dark mode support
• Share tasks with your team
• Available in 10+ languages
Privacy focused - your data stays on your device.App Icon
- Size: 512 x 512 pixels
- Format: 32-bit PNG
- Requirements: No transparency, no rounded corners
Feature Graphic
- Size: 1024 x 500 pixels
- Format: JPEG or 24-bit PNG
- Purpose: Displayed in Play Store featured section
Screenshots
At least 2 screenshots required, up to 8 allowed:
- Phone: 16:9 or 9:16 aspect ratio, 320-3840px
- Tablet: 7-inch and 10-inch (if tablet support)
Video (Optional)
YouTube video URL showcasing your app.
Step 4: Content Rating
- Click "Content rating" in dashboard
- Fill out questionnaire about app content
- Categories: violence, sexual content, language, etc.
- Receive rating (Everyone, Teen, Mature, etc.)
Content rating is required and determines which users can discover your app.
Step 5: Target Audience
- Select target age group
- Indicate if app is designed for children
- Specify if ads are shown
Step 6: App Category
- Category: Primary category (e.g., Productivity)
- Tags: Up to 5 tags for better discoverability
Step 7: Store Settings
Contact Details
- Website: Your app's website
- Email: Support email
- Phone: Optional support phone
- Privacy Policy: Required URL
External Marketing
Opt in or out of promotional campaigns.
Step 8: Build & Submit
Build AAB (Android App Bundle)
Google Play requires AAB format (not APK) for new apps:
eas.json
{
"build": {
"production": {
"android": {
"buildType": "app-bundle"
}
}
}
}bash
# Build production AAB
eas build --platform android --profile production
# Wait for build to complete (10-20 minutes)Submit to Play Store
bash
# Submit latest build
eas submit --platform android --latest
# Or submit specific build
eas submit --platform android --id <build-id>First submission must be done manually through Play Console. Subsequent updates can use
eas submit.Manual Upload
- Download AAB from EAS dashboard
- Go to Play Console → Your App → Release → Production
- Create new release
- Upload AAB file
- Fill in release notes
- Review and roll out
Step 9: Release Management
Release Tracks
- Internal Testing: Up to 100 testers, instant updates
- Closed Testing: Up to 20,000 testers
- Open Testing: Public beta, anyone can join
- Production: Full public release
Staged Rollout
Release gradually to percentage of users:
- Start with 10-20% of users
- Monitor crashes and ratings
- Gradually increase to 100%
Step 10: App Signing
Google Play App Signing (Recommended)
Google manages your app signing key:
- Opt in during first release
- Upload upload key certificate (EAS handles this)
- Google signs your app with signing key
With Google Play App Signing, you can recover if you lose your upload key!
Common Rejection Reasons
Policy Violations
- Missing privacy policy
- Requesting unnecessary permissions
- Inappropriate content
- Misleading description or screenshots
Technical Issues
- App crashes on launch
- Missing required features
- Broken links in app
- Poor performance
After Approval
Review Time
Initial review: 7 days or less. Updates: Usually faster.
Monitor Performance
- Play Console statistics
- Crash reports and ANRs
- User reviews and ratings
- Pre-launch reports (automatic testing)
Updating Your App
Increment Version
app.json
{
"expo": {
"version": "1.0.1",
"android": {
"versionCode": 2
}
}
}versionCode must be higher than previous release!Release Notes
typescript
Version 1.0.1
Bug fixes:
• Fixed crash on startup
• Improved sync performance
• Fixed dark mode issues
New features:
• Added task sorting options
• Improved offline supportSubmit Update
bash
# Build new version
eas build --platform android --profile production
# Submit update
eas submit --platform android --latestBest Practices
✅ Use internal testing
Test with internal track before production release
✅ Staged rollout
Start with 10% rollout to catch issues early
✅ Monitor crash reports
Fix crashes quickly to maintain good ratings
✅ Respond to reviews
Engage with users and address concerns