AppifyWebsite
All guides

Publish to Google Play

From your first AAB file to a live Play Store listing.

About 1–2 hours, then Google's review

Before you start

  • A Google Play developer account ($25 one-time)
  • A release AAB build (Publisher, Pro or Lifetime)
  • A privacy policy URL
  1. 1

    Create a developer account

    Go to play.google.com/console, pay the one-time $25 fee and verify your identity.

    New personal accounts must run a closed test with testers for 14 days before going public — plan for this.

  2. 2

    Build the AAB

    In AppifyWebsite choose 'Play Store (AAB)' and click Build.

    Download the .aab file when it finishes. Keep the signing key backup safe — see the signing key guide.

  3. 3

    Create the app

    Play Console → Create app. Enter the name, language, App or Game, Free or Paid.

    Accept the declarations and click Create app.

  4. 4

    Fill in App content

    Privacy policy URL, App access (give a demo login if your site needs one), Ads, Content rating questionnaire, Target audience, Data safety.

    The Store listing tab in AppifyWebsite prepares the texts and answers for you — copy them across.

  5. 5

    Store listing

    Main store listing: short and full description, app icon (512×512), feature graphic (1024×500) and at least 2 phone screenshots.

    Use the Store listing tab to generate and download these.

  6. 6

    Upload and send for review

    Test and release → Production (or Closed testing first) → Create new release.

    Upload the .aab, add release notes, then Review release → Start rollout.

  7. 7

    After approval: Google's signing fingerprint

    If your app uses Google sign-in or deep links, copy the App signing SHA-1/SHA-256 from App integrity and follow those guides' last step.

How to check it worked

  • The app shows 'In review', then 'Published'
  • You can install it from the Play Store on your phone

Common problems

'Version code already used'

Just build again — AppifyWebsite raises the version automatically each build.

Rejected for minimum functionality

Turn on app features like bottom navigation, pull to refresh, offline screen and push notifications so the app offers more than the website.

Upload signed with the wrong key

Always build with the same app. Never delete the app's signing key. Contact us if it happened.

Still stuck? Contact support — we reply within one business day.