Publish an Android app on Google Play from the US, UK or EU

To publish an Android app on Google Play in 2026 you need a developer account (one-time US$25, identity verified), an app uploaded as a signed Android App Bundle that targets a recent Android API level, a privacy policy URL, a completed Data safety form, and, for personal accounts created after November 2023, a closed test with at least 12 testers for 14 continuous days before production access. The steps are the same in the US, Canada, UK, Ireland, Australia and the EU; only tax and trader details differ. App Builder Agent produces the signed APK and AAB with one click, so the technical part is the short part.

Most first-time publishers get stuck not on the app but on the Play Console: which account type to pick, why the "Production" track is greyed out, what to put in the Data safety form, why the upload was refused. This guide walks the whole path in order, with the rules that apply to developers in North America, the UK, Ireland, Australia and the EU stated plainly. If you have not built the app yet, start with the APK app builder page; if it is built, read on.

Step 1: the developer account

• Fee - Google charges a one-time US$25 registration fee, as of 2026. It is charged in your local currency at Google's rate; there is no annual renewal.
• Account type - personal or organization. A personal account is fine for individuals and sole traders. An organization account is for registered companies and needs business verification, including a D-U-N-S number as of 2026, which can take a couple of weeks to obtain if you do not already have one. Choose carefully: the type affects the testing rule below.
• Identity verification - every account verifies the developer's identity with an official ID and, for organizations, business documents. Your developer name, and for organization accounts the address, appear on the store listing. Allow a few days.
• Payments profile - needed only if you sell paid apps or in-app items. Free apps skip it. UK, Irish, EU and Australian developers who sell will be asked for VAT/GST details.
• EU trader status - if you are established in the EU or sell to EU users, Play asks you to declare whether you act as a trader, and shows trader contact details on the listing, as of 2026. Declare honestly; a small business selling anything is a trader.

Register the account on the first day, not the last. Verification, and for personal accounts the 14-day test, are the two waits that decide your launch date.

Step 2: the 12 testers for 14 days rule

This is the rule that surprises everyone. Personal developer accounts created after November 2023 cannot publish to production until the app has run a closed test with at least 12 testers opted in for 14 continuous days. After that you apply for production access and answer a few questions about the test. Organization accounts are exempt.

• Create a closed testing track and add a tester list (Google account emails) or a Google Group.
• Share the opt-in link; each tester must accept it and install the app. Only opted-in testers count, and the 14-day clock runs continuously, so recruit 15 or more to be safe.
• Friends, family, colleagues and customers all qualify. Testers need Android phones; the app does not need to be finished, only installable and usable.
• Use the two weeks well: ship fixes to the same track, and ask testers for one sentence of feedback each. You will need to describe the testing in the production access application.

If you built the app with App Builder Agent, the test APK from the preview header is useful before this stage for your own phones, but the closed test needs the signed AAB uploaded to Play, which is the next step.

Step 3: the signed AAB, version and target API level

Google Play requires new apps to be uploaded as an Android App Bundle (AAB), signed with an upload key, with a package id that never changes and a version code that increases with every upload. Apps must also target a recent Android API level; Google raises the minimum each year and refuses uploads that fall behind.

In App Builder Agent this is one message and one click. Tell the agent your package id, app name and version; it sets up a per-project signing key, kept encrypted with the project, and the signed build produces both an APK and an AAB with an auto-incrementing version code. You can download a backup of the keystore. The signed APK and AAB guide explains package ids and version codes in detail.

• Play App Signing is on by default for new apps: you upload the AAB signed with your key and Google re-signs it for devices. This is normal and expected.
• Same key every time. Updates must be signed with the same key or Play refuses them. Keeping the key with the project is exactly what makes updates painless; keep the downloaded backup somewhere safe as well.
• Target API level. The builder targets a current Android version; if Google raises the requirement next year, ask for a rebuild.

Step 4: privacy policy, Data safety and the content forms

Every app on Google Play needs a privacy policy URL and a completed Data safety form, even an app that stores nothing. These are the two most common rejection reasons, and they must agree with each other and with the app.

• Privacy policy URL - a public web page that says what the app collects, why, and how a user can contact you and request deletion. App Builder Agent can publish a policy page from the same project at a link on appbuilderagent.com; the privacy policy guide has a checklist and a prompt.
• Data safety - a questionnaire about each data type (name, email, location, photos and so on): collected or not, shared with third parties or not, encrypted in transit, deletable on request. If the app uses a hosted backend with accounts, you collect at least an email or a name; say so.
• Account deletion - apps with sign-up must offer a way to delete the account, in the app and via a web link. Ask the agent for a Delete account button in Settings before you fill in the form.
• Content rating - a short questionnaire that produces age ratings for each region (ESRB for the US and Canada, PEGI for the UK, Ireland and the EU, ACB for Australia).
• Target audience and ads - state whether the app is for children and whether it shows ads. Apps aimed at children have stricter rules; avoid claiming a child audience unless you mean it.
• Permissions - camera, location, contacts and SMS permissions need a stated purpose. If the agent added a permission for a feature you removed, ask it to take the permission out.

Step 5: the store listing and review

• Assets - a 512 px icon, a 1024x500 feature graphic and at least two phone screenshots. The browser preview's phone frame gives clean screenshots. The icon and name guide covers the icon.
• Text - a title of up to 30 characters, a short description of 80 characters that says what the app does, and a full description written for a person searching, not for the reviewer.
• Countries - choose where the app is available. If you only serve one country, say so; it reduces support noise and legal exposure.
• Review notes - if the app has a login, provide test credentials in the notes. Reviewers who cannot get past the login screen reject the app.
• Review time - a first release commonly takes from a few hours to about a week; holidays and policy changes stretch it. Updates are usually faster. Nobody can promise an outcome, so plan a launch date after approval rather than before.

After approval, releases go out to the production track in stages if you want them to; a 20 percent rollout for a day catches crashes before everyone sees them.

Region notes for the US, Canada, UK, Ireland, Australia and the EU

• United States and Canada - the process is the baseline described above. If your app collects personal data from California residents, the privacy policy should cover CCPA rights; Canadian developers should reference PIPEDA in the notice.
• United Kingdom and Ireland - UK GDPR and the EU GDPR respectively apply to any app that processes personal data. Your privacy notice needs a lawful basis and a contact for rights requests; Play's Data safety answers should match it exactly.
• EU generally - the trader declaration and contact details on the listing apply under the Digital Services Act, and VAT is added to Google's fees where applicable. Localise the listing if you sell in more than one language; a German listing for German users noticeably improves installs.
• Australia - the Privacy Act applies to most businesses processing personal data; the content rating uses the ACB scale. Google's fee is charged in AUD at the day's rate.

The app itself needs none of this to be region-specific; the same AAB serves every country. Apps with accounts and a settings screen with account deletion are the most common shape people publish, and the login and dashboard apps in the gallery show what the finished flow looks like. Build yours, ask for the signed AAB, register the account, and start the 14-day test the same week; the review will be waiting for you at the end of it.

Frequently asked