How to publish your website app on Google Play

APK vs AAB

An APK installs directly on a phone — perfect for sharing by link, QR code or email. Google Play, however, only accepts AAB files for new apps. Play turns the AAB into optimised APKs for each device. With Web to App Creator, free builds give you an APK; Pro builds the AAB.

Your signing key matters

Every update must be signed with the same upload key as the first release. Pro keeps one key per account and signs every build with it, and you can download a backup. Turn on Play App Signing in the Console (it's the default) so Google holds the app-signing key and a lost upload key can be reset.

The 12 testers / 14 days rule

Personal developer accounts created after November 2023 must run a closed test with at least 12 testers who stay opted in for 14 continuous days before they can apply for production. Organisation accounts are exempt.

• Use a Google Group or email list for testers — each must accept the opt-in link and install the app.
• Testers should actually open the app over the two weeks; Google asks about tester feedback when you apply.
• Count days carefully: the clock is about testers being opted in, not the date you uploaded. Our closed testing calculator works out the earliest date you can apply.

Store listing checklist

• App name — up to 30 characters.
• Short description — up to 80 characters; the first thing people read.
• Full description — up to 4,000 characters. Draft one with the app description generator.
• Icon — 512 × 512 PNG.
• Feature graphic — 1024 × 500.
• Screenshots — at least 2 phone screenshots. Frame them with the screenshot mockup tool.
• Privacy policy URL — required for almost every app.

Data safety and content rating

Describe what your website collects — accounts, orders, analytics, ads — because the app shows it. Be accurate: mismatches between the data-safety form and your privacy policy are a common reason for rejection. The content rating questionnaire takes about five minutes.

Avoiding "webview spam" rejections

Google rejects apps that are just a website with nothing added, or that show content the developer doesn't own. To stay clear:

• Publish only your own site (or a client's, from the client's account).
• Make the site genuinely mobile-friendly and fast.
• Add app value: a native tab bar, push notifications, offline screen, a focused start page.
• Don't publish several near-identical apps.