How to publish your app on Google Play

This is where most app projects stall: the app builds fine, but the Play Console's forms and policies feel like a maze. Here is the whole path, in order, with the exact things Google checks.

What you need before you start

• An AAB file (Android App Bundle) — Google Play's required upload format. Not sure what that is? Read APK vs AAB explained.
• A Google Play developer account — a one-time $25 registration at play.google.com/console. Google verifies your identity; this can take a couple of days.
• A privacy policy URL — mandatory for every app. If you built your app with AppifyWebsite, you can list your own privacy page, or adapt ours as a template.
• Store assets — a 512×512 icon, a 1024×500 feature graphic, and at least two phone screenshots.

Step 1: Create the app entry in Play Console

In the Play Console, click "Create app". You'll choose the app name (30 characters max), default language, whether it's an app or a game, and free or paid. Paid can't be changed later, so start free if unsure.

Step 2: Fill in the store listing

• Short description (80 characters) — front-load what the app does.
• Full description (4000 characters) — describe features, not keywords. Don't paste unrelated keywords; that's a metadata violation.
• Graphics — icon, feature graphic, screenshots. Screenshots of your actual app, not stock photos.

Step 3: Content rating questionnaire

A short questionnaire about violence, gambling, ads and similar topics. Answer honestly — mismatches with your actual content are a rejection reason. Most business and content apps get "Everyone" or "Everyone 10+".

Step 4: Data safety form

Declare what data your app collects and whether it's shared. Be accurate: if your website uses analytics or cookies, say so. You must link your privacy policy here. Google cross-checks claims against what the app does, and contradictions delay review.

Step 5: Choose countries and upload

Select the countries, then upload your AAB under Production (or start with Internal testing to check everything on a device first — recommended). Every upload needs a higher version number than the last; AppifyWebsite handles version numbering automatically on each build.

Step 6: Review and rollout

First submissions usually review within a few days, longer for new accounts. If rejected, Google names the policy — fix that specific item and resubmit.

The most common rejection reasons

• Minimum functionality — a plain website wrapper with nothing added. Fix: native navigation, push notifications, offline support, a splash screen.
• Metadata issues — keyword stuffing, misleading screenshots, or the app not matching its description.
• Privacy gaps — missing privacy policy, or a data safety form that contradicts the app's behaviour.
• Broken functionality — the app doesn't load or has dead sections on the reviewer's device. Test your site on a phone connection first.

After publishing

Updates ship through the same console: bump the version, upload a new AAB, submit. When you change your website, the content updates itself inside the app — you only rebuild when you change app features or branding.