Submit web app to Google Play: the account, the test, the listing, the bundle
Anticode's Android project gives you most of what Google Play needs from the app itself: a signed-ready Capacitor project, a 512×512 icon and a 1024×500 feature graphic. The rest happens in Play Console under your own account: identity checks, a closed test if your account is new and personal, the Data safety form, the listing and the upload of your signed bundle.
Why many owners start with Play
Anticode's store checklist points out that Google Play is usually less strict than Apple about apps that mainly show a website, so many owners publish there first. That isn't a licence to ship a thin app: Google still has quality and policy rules, and a listing that offers nothing beyond the site won't earn installs anyway. But the path is shorter, and Android Studio runs on Windows, macOS and Linux, so no Mac is needed.
Step by step
- Create a developer account at play.google.com/console, pay the one-time registration fee and verify your identity. The checklist doesn't quote the fee because it changes.
- Build the bundle. Open the Android project in Android Studio, create your upload key and generate a signed Android App Bundle; see Android Studio.
- Create the app in Play Console with its name and default language, and confirm the declarations it asks for.
- Fill in App content, including Data safety and the content rating questionnaire (below).
- Write the store listing and add the graphics.
- Upload the
.aabto a testing track, turn on Play App Signing, and run your test. - Apply for production access when your account requires it, then promote the release.
The closed-test rule for new personal accounts
Google's testing requirements say a newly created personal developer account must run a closed test with at least 12 testers who stay opted in for 14 consecutive days before it can apply for production access. Plan for it: ask customers, friends or staff early, and use those two weeks to fix what testers notice. Anticode's checklist flags the rule but tells you to check Google's current numbers, which have changed before.
Data safety
Every app on Google Play, testing tracks included, must complete the Data safety form, according to Google's Data safety help, and a privacy policy is required to complete it even if you collect nothing. The form asks which data types the app collects or shares, why, whether collection is optional, whether data is encrypted in transit and whether people can ask for deletion.
The checklist's privacy item gives you a head start from your published forms: if they collect names, email addresses, phone numbers or messages, it suggests declaring contact information (and messages as user content), linked to the person and used for app functionality; pick the matching categories in Google's form. It also notes that the site sets no cookies and that Anticode's visit counts keep nothing about the visitor. For the privacy policy URL, Anticode's per-site Privacy Policy page, written from what the site does, is a starting point to review.
The listing and its assets
| Asset | Google's requirement | From the download or the checklist |
|---|---|---|
| App icon | 512×512 PNG | store/ includes one in your colours |
| Feature graphic | 1024×500, JPEG or PNG without transparency | store/ includes one |
| Screenshots | At least two to publish | Take them in the emulator |
| Short description | Up to 80 characters | Your meta description, cut to fit, is suggested |
| App name | Fits the store limit | Checked against your page title, 30 characters |
Google's preview assets guide has the full specifications. Write the full description yourself; the site's copy is a good source, but describe the app, including the share button and the booking reminders if your site takes bookings.
Capacitor, not a Trusted Web Activity
Some guides to publishing a PWA on Google Play use a Trusted Web Activity, which opens the site in Chrome inside an app shell. Anticode's export takes a different route: a Capacitor app that loads your live site in a WebView and adds native features through its own plugin. A TWA path, with the asset links file it needs, isn't built. The practical upshot is the same in one respect: publishing in Anticode updates the app's content without a new release.
Limits
- No Play Console access. Anticode doesn't create accounts, upload builds or answer forms for you.
- No screenshots or full description are generated.
- Push notifications aren't included; they'd need your own Firebase project.
- Approval is Google's. The checklist reduces avoidable problems; it doesn't decide outcomes.
The download is described on the Capacitor project page, Apple's side on App Store requirements, and the overall decision in turning a website into an app. If a store listing isn't essential, every site already installs from the browser.
Questions people ask
Can I skip the closed test?
Not on a new personal account, under Google's current rules. Organisation accounts are treated differently; check Google's page for your case.
Do I need a privacy policy if my site has no forms?
Yes. Google requires one to complete the Data safety form, even when you declare that nothing is collected.
Will my app update when I edit the site?
Its content will, because it loads the live site. A new icon, name or version needs a new bundle and release.