What is Google Play Store submission?
Google Play Store submission is the process of publishing your Android app through Google's distribution platform. Compared to Apple's App Store, the process is more permissive — a one-time $25 USD developer fee (not annual), typically faster review times, and more lenient initial approval — but it still requires a complete set of materials and a properly configured Play Console account before you can ship.
The deliverable is a signed Android App Bundle (AAB, the modern format) or APK uploaded to Play Console, alongside store listing assets — screenshots, a feature graphic, description, content rating, and a data safety section declaring what data your app collects.
Google's release tracks — internal testing, closed testing (alpha), open testing (beta), and production — allow you to control rollout stages, releasing to internal QA before exposing to the general public.
When does your app need it?
- Your app is ready for public distribution on Android devices
- You're setting up a beta programme via an internal or closed testing track before production release
- You need to configure release tracks to manage a phased rollout to a percentage of users
- Your app is already live and needs an update submitted through the review pipeline
- You need to comply with Google's target API level requirements (updated annually) for an existing app
- You're setting up Play Console for the first time and need accounts, signing keys, and tracks configured correctly
How much does it cost?
Google Play Store submission typically adds 3–5 hours of developer time — roughly from $1,000 AUD.
This covers: Google Play developer account setup (if not already registered), keystore and app signing configuration, Play Console listing creation, store listing assets and description, content rating questionnaire, data safety section completion, AAB build and upload, and release track configuration.
Complexity increases if the app uses Play Billing (in-app purchases, subscriptions), if you need to configure multiple release tracks with different APK variants, or if a policy violation triggers a rejection that requires remediation and resubmission.
How it's typically built
Android apps are built and signed using Android Studio or a CI/CD pipeline (Bitrise, GitHub Actions). The signing keystore — a file containing the private key used to sign releases — must be kept secure and backed up. If you lose it, you cannot update the app without creating a new listing.
Google Play App Signing (GPAS) is now the recommended approach: you upload an upload key-signed bundle, and Google re-signs it with the distribution key they manage on your behalf. This protects against keystore loss.
The data safety section requires you to declare every type of data the app collects (location, contacts, health info, etc.), how it's used, whether it's shared with third parties, and whether users can request deletion. This must be accurate — mismatches between declared behaviour and actual behaviour are a policy violation.
Questions to ask your developer
- Has the Google Play developer account been registered? The $25 USD fee is one-off, but the account setup process has several steps that take time to process.
- Where is the signing keystore stored? Loss of the keystore means loss of the ability to update the app. It must be backed up securely and the location documented.
- Is Play App Signing enabled? It should be for new apps — upload key loss is recoverable; distribution key loss is not.
- What does your data safety declaration cover? Be thorough — inaccurate declarations are a common reason for policy strikes.
- Are you targeting the current required API level? Google enforces minimum target SDK levels; apps that don't meet the current requirement can't be updated or newly installed.
See also: iOS App Store submission · Analytics setup · App cost calculator