To launch on Google Play from the UK in 2026, the app being finished is the easy part. The part that trips up first time founders is everything around it: the developer account, the identity checks, the closed testing rule that Google introduced for new personal accounts, and a review process that rejects for reasons nobody warned you about. We have shipped apps to Google Play many times, and almost every avoidable delay came from not knowing a step existed until it blocked us. This guide walks the whole process in order, UK specific where it matters, with the traps marked so you do not hit them the week you planned to go live.
How to launch on Google Play from the UK, step by step
To launch on Google Play from the UK you register a Play Console developer account, complete Google’s identity and address verification, prepare your store listing and app content declarations, run the required closed test if you are on a new personal account, then submit a production release for review. Budget two to three weeks for the parts outside your control, not two to three days.
That timeline surprises people. The build is done, the founder assumes they press a button and the app appears. In reality the verification, the testing requirement, and the review each add days you cannot compress, and they run partly in sequence. The single most useful thing you can do is start the account and verification steps early, well before the app is finished, so the waiting happens in parallel with development instead of after it.
Step 1: choose the right account type and register
Your first real decision is personal versus organisation account, and it matters more than it looks. A personal account is faster to open but, since Google’s 2023 to 2024 policy changes, new personal accounts must complete a closed test with real testers before they can publish to production. An organisation account, tied to a registered company, avoids some of that friction but requires a D-U-N-S number, which takes time to obtain if you do not have one.
For a UK founder trading through a limited company, the organisation route is usually worth the extra setup, because it puts your company name on the listing rather than your personal name and sidesteps the harshest testing gate. Either way there is a one time registration fee of 25 US dollars, charged in dollars even from the UK, so expect a small currency conversion on your card. Register at the Google Play Console and do it now, because verification cannot start until the account exists.
Step 2: pass identity and address verification
This is the step that quietly delays more UK launches than any other, because you cannot rush it and Google will not publish anything until it clears. New accounts must verify the developer’s legal name, a physical address, and contact details, and Google may ask for a document to confirm them. For an organisation account, you also verify the company.
The trap is that Google posts or emails verification prompts on its own schedule, and if you miss one, the clock resets. Check the Play Console notifications regularly during this window, respond the same day, and make sure the name and address you enter exactly match your official documents. A mismatch between your Companies House record and what you typed is a common rejection, and it is entirely avoidable. Start this the moment the account is open, because everything downstream is blocked until it is done.
Step 3: run the closed test (if your account requires it)
If you are on a new personal account, Google requires a closed test with at least 12 testers who stay opted in for 14 continuous days before you can apply for production access. This rule exists to filter out low effort and fraudulent apps, and it is the single biggest surprise for founders who expected to publish immediately.
Twelve real testers for fourteen unbroken days is harder than it sounds when you are pre launch and have no users yet. Line them up in advance: friends, early waitlist signups, colleagues, anyone with an Android device willing to install and keep the app on their phone. Create a closed testing track in the Play Console, add their Google account emails, and confirm they actually opt in, because a tester who accepts the invite but never installs does not count. Starting this two weeks before your target launch is the difference between shipping on time and slipping a fortnight. For a broader view of getting an app through the gates on both stores, our guide on preparing for app store review in the UK covers the review mindset that applies here too.
Step 4: build the store listing and content declarations
While the test runs, prepare the listing, because a strong one is not optional. You need a title, a short and full description, a feature graphic, screenshots for phone and, if relevant, tablet, an app icon at the right resolution, and a privacy policy hosted at a live URL. That privacy policy is mandatory, not a nice to have, and Google checks that the link works.
The declarations catch people out. You must complete the Data Safety form, honestly describing what data your app collects and shares, and the content rating questionnaire. Getting the Data Safety form wrong, by understating what you collect, is a rejection risk and, for a UK app handling personal data, a UK GDPR problem on top. Fill it in to match what your app actually does, per the Information Commissioner’s Office guidance on transparency, not what you wish it did. If your listing mentions data handling in prose, keep it plain: what you collect, why, and who you share it with.
Step 5: submit for production review and handle rejection calmly
With verification cleared, testing satisfied, and the listing complete, you promote a release to the production track and submit for review. Review for a new app typically takes a few days but can stretch longer, especially for a first submission or an app touching sensitive permissions. Do not book a launch event for the day after you submit.
If you are rejected, and first submissions often are, read the reason carefully rather than resubmitting blindly. The frequent UK causes are a broken or missing privacy policy link, a Data Safety form that does not match app behaviour, requesting permissions you do not justify, or metadata that overpromises. Fix the specific issue, reply through the Play Console, and resubmit. A rejection is a checklist item, not a verdict, and calm founders clear it in a day while panicked ones waste a week guessing.
The UK specific things to get right
A few points matter more because you are launching from Britain. Your privacy policy and Data Safety declarations sit under UK GDPR, so they must be accurate, not decorative, and the Information Commissioner’s Office expects genuine transparency about data collection. If you take payments for digital goods inside the app, Google’s billing and its service fee apply, and you should model that into your pricing before launch, not after. And if your app is aimed at or accessible to children, the UK’s Age Appropriate Design Code raises the bar on what you must declare and how you handle data.
None of these are blockers if you plan for them. They become blockers when a founder treats the UK legal layer as an afterthought and gets stopped at review. If you are unsure whether your declarations hold up, that is a good thing to check before you submit, not after.
Plan the boring parts early and you will launch on time
The pattern in every delayed launch we have seen is the same: the app was ready, but the account, verification, testing, and review were treated as a formality and started too late. Reverse that. Open the account and begin verification while the app is still in development. Recruit your testers weeks ahead. Write the privacy policy and fill the Data Safety form honestly and early. Do that, and the launch itself becomes anticlimactic in the best way, which is exactly what you want.
If you are building an app and want the store launch handled properly rather than improvised the week before, send us a project brief. Getting an app onto Google Play cleanly, UK compliance and all, is a process we run often, and it is a lot less stressful when someone who has done it before is steering. For the broader picture of shipping and running an app after launch, what an app really costs to maintain is worth a read too.
.webp)
.webp)
