App Test Bench
← Guides

Preparing for production

Passing the testing requirement gets you the application form. These are the things that decide whether it's approved.

Applying for production access

Once 12 testers have been opted in for 14 continuous days, Play Console shows the production access application on your dashboard. It asks about your testing: what feedback you gathered, what you changed as a result, and how you'll keep improving the app.

Answer these in detail and specifically about your app. Generic or empty answers are a common reason for rejection even when the tester numbers are met.

Technical readiness

  • Target API level — Play enforces a minimum target SDK for new apps and updates. Set targetSdk to the current requirement.
  • App Bundle, signed by Play — enrol in Play App Signing and keep your upload key safe.
  • 64-bit support — required; if you ship native libraries make sure arm64-v8a is included.
  • No crashes on launch — the fastest way to fail review. Our in-depth tier captures crash and ANR logs from each device so you see these before Google does.

Store listing

  • App name (30 chars), short description (80), full description (4000).
  • App icon 512×512, feature graphic 1024×500.
  • Screenshots: at least 2 per form factor you support, phone screenshots required.
  • Privacy policy URL that actually resolves and covers what your app collects.

Keep the listing honest — claims your app can't back up, or screenshots that don't match the app, are policy violations.

Policy checks worth doing yourself

  • Data safety form matches reality — what you declare must match what your app and its SDKs actually collect.
  • Permissions are justified — sensitive permissions (location, camera, all-files access) need a clear in-app purpose.
  • Account deletion — if users can create an account, you must offer a way to delete it, including a web URL.
  • Ads and IAP declared correctly in App content.

Rolling out

  1. Create a release on the Production track with the same (or newer) bundle you tested.
  2. Choose your countries and regions.
  3. Consider a staged rollout (start at 10–20%) so a bad build can be halted before it reaches everyone.

Want help with all of this?

Our Concierge tier includes 1:1 guidance through production access — we review your listing and release with you and stay on it until your app is live.