Google Play Store Requirements Checklist: Complete Guide 2025

Submitting to Google Play requires attention to numerous guidelines, policies, and technical requirements. This comprehensive checklist ensures your Android app passes review on the first submission.

Google Play vs App Store Differences

Key distinctions:

• Google Play review is typically faster (hours to days vs days to weeks)
• More flexible content policies in some areas
• Different privacy disclosure requirements
• Unique testing requirements (closed/open testing tracks)
• Different app signing requirements

Pre-Submission Technical Requirements

1. App Bundle and APK Requirements

Format specifications:

• Preferred: Android App Bundle (.aab) format
• Legacy: APK files (being phased out for new apps)
• Max size: 150 MB for app bundle, 100 MB for APK
• Expansion files: Up to 2GB if additional assets needed
• 64-bit support: Required for all apps

2. Target SDK Version

Critical requirements:

# build.gradle requirements

android {
    compileSdk 34           // Latest

    defaultConfig {
        minSdk 21           // Minimum API 21 (Android 5.0)
        targetSdk 34        // Must target recent version
                           // (within 1 year of latest)
    }
}

3. App Signing

Google Play App Signing:

• Enroll in Play App Signing (recommended)
• Keep upload key secure
• Google manages app signing key
• Enables easier key recovery

4. Required Permissions

Permission best practices:

• Request only necessary permissions
• Provide clear explanation for sensitive permissions
• Implement runtime permission requests
• Remove unused permissions before submission

Store Listing Requirements

1. App Metadata

Title and Description

• Title: Maximum 30 characters
• Short description: 80 characters
• Full description: 4,000 characters
• Clear, accurate description of functionality
• No misleading claims or clickbait
• Keywords naturally integrated (no keyword stuffing)

Graphics Assets

Required assets:

App Icon:
- 512 x 512 px
- PNG format (32-bit)
- No alpha/transparency

Feature Graphic:
- 1024 x 500 px
- PNG or JPEG
- Represents app brand

Phone Screenshots:
- Minimum: 2 screenshots
- Recommended: 4-8 screenshots
- JPEG or PNG
- Dimensions: 16:9 or 9:16 aspect ratio
- Min: 320px on short edge
- Max: 3840px on long edge

Tablet Screenshots (if supporting tablets):
- 7-inch and 10-inch screenshots
- Different from phone screenshots

TV Screenshot (if Android TV):
- Required for TV apps

2. Categorization

Category selection:

• Choose most relevant primary category
• Optional secondary category
• Accurate tags for discoverability
• Content rating questionnaire completion

3. Contact Information

Required details:

• Developer email (publicly visible)
• Developer website (optional but recommended)
• Physical address (required for paid apps/in-app purchases)
• Privacy policy URL (mandatory for most apps)

Privacy and Data Safety

Data Safety Section

Google Play's transparency requirements:

What Data is Collected

• Personal info: Name, email, address, phone
• Financial info: Payment info, purchase history
• Location: Approximate or precise location
• Photos and videos: User's photos/videos
• Files and docs: User files
• Messages: Emails, SMS, chat messages
• App activity: In-app actions, search history
• Device or other IDs: Advertising ID, device ID

How Data is Used

• App functionality
• Analytics
• Developer communications
• Advertising or marketing
• Fraud prevention, security
• Personalization
• Account management

Data Sharing

• Shared with third parties
• Transferred to other countries
• Sold to third parties (rare)

Security Practices

• Data encryption in transit
• Data encryption at rest
• Users can request data deletion
• Independent security review conducted

Privacy Policy Requirements

When privacy policy is required:

• Apps that collect personal or sensitive user data
• Apps with user accounts
• Apps requesting sensitive permissions
• Apps with in-app purchases
• Apps using third-party analytics/advertising

Privacy policy must include:

• What data is collected
• How data is used
• How data is shared
• User rights and choices
• Data retention and deletion
• Contact information

Content Policy Compliance

1. Prohibited Content

Apps cannot contain:

• Sexual content or profanity
• Hate speech or violence
• Illegal activities promotion
• Gambling with real money (without proper licensing)
• Unauthorized intellectual property
• Deceptive behavior or fraud
• Malware or malicious code

2. Restricted Content

Special requirements:

• Financial services: Proper licensing and compliance
• Health apps: Medical disclaimer if providing advice
• Real money gambling: Restricted to approved territories
• User-generated content: Moderation system required
• Dating apps: Age restrictions and safety features

3. Families Policy

If targeting children under 13:

• COPPA compliance required
• No behavioral advertising
• Age-appropriate content only
• Parental gate for external links
• No sensitive permissions without justification
• Teacher Approved program consideration

Functionality Requirements

1. App Quality

Minimum standards:

• App must be stable (no crashes on launch)
• All features must work as described
• No "under construction" or placeholder content
• Proper back button behavior
• Battery and network efficiency
• No deceptive ads or interstitials

2. User Experience

Design guidelines:

• Follow Material Design principles (recommended)
• Responsive design for different screen sizes
• Appropriate text sizes and touch targets
• Clear navigation
• Proper error handling and messages

3. Testing Requirements

Before public release:

• Test on multiple devices and Android versions
• Use Internal testing track for team
• Use Closed testing for beta testers
• Consider Open testing for wider feedback
• Review crash and ANR reports

Monetization Requirements

1. In-App Purchases

Google Play Billing requirements:

• Use Google Play Billing API for digital goods
• Clear pricing display
• Proper subscription management
• Refund policy clearly stated
• No alternative payment methods for in-app digital content

2. Advertising

Ad policy compliance:

• Ads must be clearly distinguishable from content
• No ads that interfere with functionality
• No unexpected or deceptive ads
• Proper ad format for families apps
• Disclose if ads are personalized

3. Subscription Requirements

If offering subscriptions:

• Clear terms and pricing
• Trial period disclosure
• Easy cancellation process
• Billing frequency clearly stated
• Renewal terms explained

Technical Quality Standards

Android Vitals

Key metrics to monitor:

Crash Rate:
- Target: < 1.09% crash rate
- Measure: Crashes per user session

ANR Rate (App Not Responding):
- Target: < 0.47% ANR rate
- Ensure responsive UI thread

Excessive Wakeups:
- Target: < 10 wakeups per hour
- Optimize background processes

Stuck Wake Locks:
- Target: < 1 hour per day
- Release wake locks properly

Performance Optimization

• App startup time: < 5 seconds
• Smooth animations: 60 fps target
• Reasonable battery consumption
• Efficient network usage
• Appropriate memory footprint

Common Rejection Reasons

1. Policy Violations

• Misleading app name or description
• Copied content from other apps
• Inappropriate content
• Privacy policy missing or inadequate
• Unauthorized use of brand names

2. Technical Issues

• App crashes on startup
• Missing required functionality
• Outdated target SDK version
• Missing 64-bit support
• Oversized app bundle

3. Data Safety Issues

• Inaccurate data safety declarations
• Privacy policy doesn't match declarations
• Collecting data without disclosure
• Third-party SDKs not properly disclosed

Pre-Launch Checklist

Final Review Before Submission

• ✓ App bundle built and tested
• ✓ Target SDK is current
• ✓ All graphics assets uploaded
• ✓ App description is accurate and compelling
• ✓ Privacy policy URL added and accessible
• ✓ Data safety section completed accurately
• ✓ Content rating questionnaire filled
• ✓ App tested on multiple devices
• ✓ No crashes or major bugs
• ✓ All required permissions justified
• ✓ Contact information is current
• ✓ Pricing and distribution set
• ✓ In-app products configured (if applicable)
• ✓ Tested with internal/closed testing track

Post-Submission Process

Review Timeline

• Initial review: Usually within hours to a few days
• Updates: Faster than initial submissions
• Policy review: May take longer if flagged

If Rejected

1. Read rejection reason carefully
2. Check Google Play Console for specific policy violations
3. Fix all identified issues
4. Test thoroughly
5. Submit appeal or resubmit
6. Respond to reviewer comments if needed

Maintaining Compliance

Regular Updates

• Update target SDK annually
• Fix bugs and crashes promptly
• Keep privacy policy current
• Update data safety declarations when adding features
• Monitor Android Vitals dashboard
• Respond to user reviews

Support Page Requirements

While not always required, having a professional support page improves user experience and can help with policy compliance:

Essential Support Page Elements

• Contact information or contact form
• FAQ section
• Privacy policy link
• Terms of service
• Data deletion instructions
• Refund policy

Conclusion

Successfully publishing on Google Play requires attention to policies, technical requirements, and user experience. This checklist ensures you meet all requirements, but remember that policies evolve—always check the latest Google Play Console documentation before submission.

Need compliant support and privacy pages for your app? Our generator creates Google Play-compliant pages in minutes, with secure hosting and easy customization options.