Skip to content

Google Play requirements checklist for web-to-app builds

Everything Play Console asks for before a web-based Android app goes live, in the order you will meet it.

Publishing a web-based app is not harder than any other app, but the Play Console asks for a lot of things in a specific order. Work through this list once and keep it for the next app.

Account and app

  • Google Play developer account (one-time fee) with identity verification completed.
  • App name, default language and whether it is free or paid (free apps cannot later become paid).

Technical

  • AAB signed with your keystore (ApkZio provides this).
  • Target API level at or above Play’s current requirement (ApkZio builds target the latest).
  • 64-bit support (included).
  • A unique package name you will keep forever (set it in the builder before the first upload).

Store listing

  • Short description (80 characters) and full description (4000 characters).
  • App icon 512×512 PNG, feature graphic 1024×500.
  • At least two phone screenshots; a tablet screenshot if you declare tablet support.

Policy forms

  • Privacy policy URL on your own domain.
  • Data-safety form: declare what the app collects. A plain website wrapper usually collects nothing itself; declare what your website and enabled services (push, ads) collect.
  • Content rating questionnaire.
  • Ads declaration (yes if you enabled AdMob).
  • Target audience and, if children are included, families policy compliance.

Before you press publish

  • Run an internal test with a few devices.
  • Check that every page opens and that external links behave as intended.
  • Keep the keystore backed up; you will need it for every update.
Related

Create Your App Without Coding

Turn your website into a professional Android app today. Start for free and launch your app in just a few simple steps.

Start with a free build and take your website to Android today.

Build my app - free