Mobile Apps
What Do You Need to Publish an App on Google Play?
Weps Technologies · 22/10/2026 · Updated 11/11/2026
Prepare your Google Play launch with a checklist covering account verification, testing, app bundles, store assets, privacy, Data safety and app review.

What do you need to publish an app on Google Play
To publish an Android app on Google Play, prepare a verified developer account, a release-ready Android App Bundle, accurate store listing assets, privacy and Data safety information, and the declarations and reviewer access your app needs. Some personal accounts must also complete a qualifying closed test before applying for production access. Uploading a build is one step in the process, not the finish line.
Requirements checked on 11 November 2026. Google updates its policies, so review the linked documentation and your Play Console dashboard before submitting a release.
Start with an account your business controls
Google charges a one-time US$25 developer registration fee. The account holder must be at least 18 and complete the required verification. This fee is separate from development, hosting, maintenance and any applicable charges on sales (Google: create a developer account).
Choose the account type that accurately represents the publisher. Organization accounts generally require a D-U-N-S number and matching organization details. Google documents limited alternatives for unsupported regions and known government bodies; these are not a general workaround. Obtaining a D-U-N-S number can take up to 30 days, so start early (Google: organization account details).
For a client project, our recommendation is to use an account controlled by the client and invite the development team with appropriate access. Decide who controls the recovery methods, support email, signing records and future releases before development ends.
Check whether closed testing applies
For personal accounts created after 13 November 2023, Google requires at least 12 testers opted in continuously for the preceding 14 days before applying for production access. The application asks about testing and readiness. Internal testing does not replace this closed test. The documented requirement is specific to those personal accounts, not a blanket rule for every organization account. Complete any device-verification task shown during setup (account setup, Google: testing requirements for new personal accounts).
Recruit people who can use the app and report problems. Keep a simple record of feedback, fixes and retests. A list of email addresses alone does not demonstrate that the product works, and finishing the test does not guarantee approval.
Prepare the release build
For a new Play app, prepare an Android App Bundle and configure Play App Signing. Protect the upload key and retain the package name, signing certificate details and release records. The upload key and Play app-signing key serve different roles (Android Developers: app signing).
As checked for this guide, new standard Android apps and updates must target Android 16, API 36, or higher. The published minimums differ for Wear OS and Android Automotive OS, which require API 35, and Android TV and Android XR, which require API 34. Existing-app availability rules are separate. Check the official requirements for your form factor before building (Android Developers: target API level requirements).
Test the build users will actually install
Test the release through a Play testing track, including sign-in, payments where applicable, notifications, permissions, uploads and offline behaviour. Practical advice from our own engineering checks: validate integrations that depend on signing certificates against the Play app-signing certificate, rather than relying only on a locally installed debug build.
Review native libraries and SDKs for 16 KB memory-page compatibility. Google’s current guidance covers apps targeting API 35 or higher on 64-bit devices and states that incompatible updates will be blocked from 1 February 2027. Check current Console notices and test compatibility now, particularly when dependencies include native code (Android Developers: 16 KB page sizes).
Prepare your store listing assets
| Asset | Current baseline |
|---|---|
| App name | Up to 30 characters |
| Short description | Up to 80 characters |
| Full description | Up to 4,000 characters |
| Store icon | 512 × 512 px PNG; maximum 1024 KB |
| Play feature graphic | 1024 × 500 px JPEG or 24-bit PNG without alpha |
| Screenshots | At least two for the listing; additional form-factor rules may apply |
| Support contact | Working support email address |
These are baseline listing specifications, not a guarantee of promotional eligibility. Show the real app experience, check the device-specific screenshot rules and avoid unsupported ranking claims or repetitive keywords. A website article cover is a different asset from an app’s Play feature graphic (listing text and contact details, listing graphics).
Make privacy statements match the app
Provide a public privacy-policy webpage and make the policy accessible in the app. It must describe the actual data practices; it is required even when an app does not access personal or sensitive data. Do not use a private document, a login-only link or a PDF as the policy URL (Google: privacy policy and user data).
Complete Data safety based on the app and all included SDKs. Review analytics, crash reporting, advertising, authentication and backend data flows with the developer. An app with no data collection still needs the declaration for public publishing. Apps exclusively on internal testing tracks have a specific exemption; that does not carry over to a public launch (Google: Data safety).
If your app enables account creation, provide an accessible account-deletion request route inside the app and a working web route outside it. Explain any legitimate retention and complete the relevant Data safety questions. Disabling or freezing an account is not the same as deleting it (Google: account deletion requirements).
Give reviewers access and complete declarations
Complete the App content tasks that apply to the product, including content rating, ads, target audience and sensitive-permission declarations. If access requires sign-in or other restrictions, provide working instructions and credentials through Play Console (Google: review declarations and access).
Before submission, have someone unfamiliar with the app follow those instructions. Check that they can reach the core features without needing a personal OTP, an unavailable employee or a broken backend. Use a controlled review account and do not put its credentials in the public listing.
Understand Android developer verification
The wider Android verification programme is distinct from the basic Play account setup. Google’s current timeline begins protections on 30 September 2026 for participating stores on certified Android 7+ devices in Brazil, Indonesia, Singapore and Thailand, with wider rollout from 2027. Check the applicable distribution guidance and Play Console status; a developer’s location alone does not decide whether their users are affected (Android Developers: developer verification).
Check readiness before submitting
| Area | Evidence to check |
|---|---|
| Ownership | Account, recovery access and release responsibilities agreed |
| Build | Release bundle tested through Play with integrations working |
| Listing | Accurate text and graphics that match the submitted version |
| Privacy | Policy, SDK inventory and Data safety answers agree |
| Accounts | Deletion routes work when the policy applies |
| Review | Reviewer can access all relevant features using supplied steps |
| Release | Required testing, declarations and Console tasks completed |
Frequently asked questions
Is the US$25 fee charged for each app?
No. It is the developer-account registration fee, not a per-app upload fee. Other product and business costs are separate (Google: account setup).
Does the 14-day test mean my app will be live on day 15?
No. It is a qualifying test for the applicable accounts. Production access and app review are separate steps, and issues can require more work (Google: testing requirements).
Do I need a website?
You need accessible policy and deletion resources where required. A large marketing website is not the same requirement. Organization verification also asks for an organization website (organization details, privacy policy, account deletion).
How long will publishing take?
Plan separately for verification, asset preparation, testing, production access and review. Do not promise a fixed public launch date until the relevant dependencies are resolved.
Plan your launch with Weps Technologies
Need help preparing the build, store listing or release checklist? Discuss your app launch with Weps Technologies. Share the app’s current stage, account type and intended launch markets so we can identify the remaining work and scope the support. Our mobile app development service covers Android and iOS apps, and our app development timeline guide explains how long the build itself can take.