Google Play Console is more complex than it first appears. This guide walks new developers through every required step, in the right order, so nothing is missed before applying for production access.
Google Play Console is the developer portal for publishing, managing, and monitoring apps on the Google Play Store. If you have never used it before, the volume of sections and requirements can be overwhelming. This guide covers only what you need to publish your first app — in the order you need to do it.
Step 1: Create and Verify Your Developer Account
Go to play.google.com/console and sign in with your Google account. You will be prompted to pay a one-time $25 registration fee. After payment, new personal accounts must complete identity verification before they can publish apps. Verification requires a government-issued ID and typically takes 1–3 business days.
Step 2: Create an App
In the Play Console dashboard, click 'Create app'. Enter your app's name, default language, whether it is an app or game, and whether it is free or paid. This creates the app entry in Play Console — you have not published anything yet, just created a container for your app's data.
Step 3: Complete the Store Listing
Under your app, navigate to Store presence > Main store listing. Required fields: short description (80 characters), full description (up to 4000 characters), screenshots (minimum 2 for phone), feature graphic (1024x500), and app icon (512x512). You cannot apply for production access without a complete store listing.
Screenshots must be real screenshots of your app. Using mockups or illustrations as screenshots violates Play Store policy and will cause rejection.
Step 4: Complete the Required Forms
Under Policy, complete the following forms: App content (content rating questionnaire, target audience, ads declaration), Data safety (declare what data your app collects and how), and Privacy policy (provide a live URL to your privacy policy). These are mandatory before production access.
Step 5: Upload Your App to the Closed Testing Track
Navigate to Testing > Closed Testing. Create a track if prompted. Upload your signed AAB or APK. This is the version that your testers will install. Set the rollout to 100% within the track.
Step 6: Add Testers and Get the Opt-In Link
Under your closed testing track, go to Testers. You can add individual Gmail addresses or a Google Group. Copy the opt-in URL and send it to all testers. They must complete the opt-in on their Android device and install the app through the Play Store.
Step 7: Monitor for 14 Days
Check your active tester count daily. If it drops below 12, the 14-day counter resets. After 14 continuous days with 12+ active testers, the production access application becomes available.
Step 8: Apply for Production Access
Navigate to your app's Production section. Click 'Apply for production access'. Complete the questionnaire with specific details about your testing period, tester count, feedback received, and changes made. Submit. Google reviews within 3–7 business days.
Common Mistakes New Developers Make
- Uploading the app to Internal Testing instead of Closed Testing
- Starting the 14-day window before all testers have enrolled
- Uploading a debug build instead of a signed release build
- Not completing the Data Safety form before applying
- Using screenshots that do not match the current version of the app
- Writing questionnaire answers that are too brief or generic
For the tester recruitment step, Gapsolvers handles everything — the Google Group, the opt-in process, and the 14 days of active participation.
Handle Step 6 With Us