Google Play Production Checklist: 5 Steps Before Going Live

Applying for Google Play production access requires more than completing the 14 day closed testing period. Your app must have all tester feedback addressed, every critical bug resolved, and full compliance with Google's latest policies before you submit the production application. Skipping any of these steps is one of the top reasons apps get rejected or delayed.

After helping clients ship over 200 apps through Google Play Console, we have seen the same avoidable mistakes cause rejections repeatedly. Developers finish closed testing and rush to apply for production without reviewing feedback, fixing issues, or updating their app build. Google's review team checks all of this, and incomplete preparation leads to wasted time and frustrated clients.

This checklist covers the 5 essential steps every developer should complete before applying for production on Google Play Console. Follow these in order and your chances of first submission approval increase significantly.

Google Play production checklist showing 5 essential steps before applying for production access on Play Console

Step 1: Respond to Every Piece of Tester Feedback

During closed testing, your testers provide direct feedback about app performance, usability, and bugs through Google Play Console. Google tracks whether developers actually engage with this feedback. Ignoring it sends a clear signal that you have not taken the testing phase seriously, and that alone can lead to rejection.

From our experience managing testing workflows for 200+ apps, we have found that responding to every single piece of feedback is one of the strongest signals you can send to Google's review team. It demonstrates active development, real user engagement, and a commitment to quality.

• Log into Google Play Console and select your app
• Navigate to Monitor and Improve, then Ratings and Reviews, then Testing Feedback
• Reply to every tester comment professionally and specifically
• Address the exact issue raised, not generic thank you messages
• If a bug was reported, confirm it has been fixed in the latest build

Professional, specific replies show Google that your app has been thoroughly reviewed and refined based on real world usage. Generic responses like "thanks for testing" do not carry the same weight.

Google Play Console tester feedback section showing developer replies to closed testing feedback

Step 2: Fix Every Bug and Issue Found During Testing

If testers identified bugs, UI problems, or performance issues, all of them must be resolved before you apply for production. Google's review team will test your app on real devices, and any unresolved issues from the testing phase will likely cause rejection.

We have seen apps rejected for issues as small as a broken back button or a slow loading screen. The review team expects a production ready experience, not a work in progress.

• Fix all critical and major bugs reported by testers
• Resolve performance issues like slow load times, ANRs, or crashes
• Implement UI and UX adjustments based on tester suggestions
• Test login, signup, and core user flows end to end
• Verify subscription and in app purchase flows work correctly
• Run the app on at least 3 different device sizes to catch layout issues

An app with unresolved issues from closed testing is significantly more likely to be rejected during Google's production review. Treat every tester report as a mandatory fix, not optional feedback.

Step 3: Upload an Updated Build Before Applying

Google closely monitors how your app evolves during the testing phase. If testers reported issues and you fixed them, upload a new build to the closed testing track before applying for production. This creates a clear record that shows Google you acted on feedback and improved the app.

From our publishing experience, apps that show at least 1 to 2 version updates during closed testing have noticeably higher approval rates compared to apps that submit the same original build. Google values iteration and active development.

• Implement all bug fixes and improvements from tester feedback
• Upload the updated APK or AAB to the closed testing track in Play Console
• Wait for the new build to go live on the testing track
• Notify testers about the update and ask them to test the latest version
• Collect additional feedback on the updated build if time allows

Keeping the app updated during testing demonstrates active maintenance and real development effort. Google's review team can see your version history, and a single static build with no updates is a weaker signal than an app that has been refined through multiple iterations.

Google Play Console release dashboard showing app version updates during closed testing phase

Step 4: Write Detailed Production Application Answers

When you apply for production access, Google asks approximately 9 questions about your testing process, tester engagement, bugs fixed, and app improvements. Your answers directly impact whether your application is approved or rejected. Vague or generic responses are one of the most common reasons for rejection.

Based on our experience helping developers pass production review, here is what works best in your application answers.

What to Include in Your Answers

• Detailed descriptions of how the app was tested and by whom
• Specific feedback examples that were received and how each was addressed
• Mention that you communicated with testers via social platforms like Facebook or Instagram for real engagement
• Highlight that additional testers including family, friends, and colleagues participated beyond the required 12
• Reference specific bug fixes and version updates made during the testing period
• Keep answers honest, short, and direct. Avoid long AI generated paragraphs

Google wants to see that real people tested your app on real devices and that you took their feedback seriously. Mentioning direct tester communication and a diverse testing group adds credibility that purely technical answers lack.

Step 5: Verify Compliance with Google's Latest Policies

Google regularly updates its developer policies, particularly around data privacy, app permissions, content restrictions, and user experience standards. Before applying for production, review the most recent policy updates to ensure your app is fully compliant. An app that was compliant 3 months ago may not be compliant today.

• Data privacy: only request permissions your app actually needs and handle user data securely
• Privacy policy: ensure your app links to a valid, accessible privacy policy
• Content policy: verify your app does not contain prohibited or restricted content
• User experience: remove unnecessary interstitial ads, forced signups, or disruptive popups
• Target API level: make sure your app targets the latest required Android API level
• Data safety section: complete the data safety form accurately in Play Console

Policy compliance is non negotiable. Even a well tested app with excellent feedback will be rejected if it violates Google's current policies. Check the Play Console policy center before every production submission.

Complete Production Readiness Checklist

Here is the full checklist to run through before clicking the production application button in Google Play Console.

# Google Play Production Readiness Checklist

# 1. Tester Feedback
[ ] Replied to every tester comment in Play Console
[ ] Addressed specific issues raised in feedback
[ ] Professional, specific replies (not generic)

# 2. Bug Fixes
[ ] All critical bugs resolved
[ ] Performance issues fixed (crashes, ANRs, slow loads)
[ ] UI/UX adjustments implemented
[ ] Core flows tested end to end

# 3. App Updates
[ ] Updated build uploaded to closed testing track
[ ] Testers notified about new version
[ ] Latest version tested and verified

# 4. Application Answers
[ ] Detailed, honest responses prepared
[ ] Tester communication methods mentioned
[ ] Diverse testing group highlighted
[ ] Specific improvements documented

# 5. Policy Compliance
[ ] Latest Google policies reviewed
[ ] Data safety section completed
[ ] Privacy policy linked and accessible
[ ] Target API level current

Frequently Asked Questions

What happens if I apply for production without fixing tester feedback?

Google can see whether you engaged with tester feedback in Play Console. Applying without responding to feedback or fixing reported issues significantly increases the chance of rejection. Always address feedback before submitting your production application.

How many app updates should I upload during closed testing?

We recommend at least 1 to 2 updates during the 14 day testing period. Each update should address real issues found by testers. This shows Google that your app is actively maintained and improving based on real feedback.

How long does Google take to approve production access?

Google typically responds within 24 to 72 hours after you submit the production access application. Well prepared applications with detailed answers and documented testing activity tend to get approved faster.

Can I apply for production right after 14 days of closed testing?

Technically yes, but we recommend waiting 1 extra day after the 14 day period ends. Use that time to verify all feedback is addressed, the latest build is tested, and your application answers are thorough. Rushing the application is one of the most common mistakes developers make.

What if my production application gets rejected?

Review the rejection reason carefully, fix the specific issue mentioned, and resubmit. Most rejections are caused by incomplete testing activity, unresolved bugs, or vague application answers. If you need professional help, our app testing and publishing team can guide you through the resubmission process.