To publish a no-code app on Google Play: register a developer account ($25 once), download the signed app bundle (AAB) from the builder's Get your app screen, create the app in Play Console, fill in the listing and the data-safety form, upload the bundle to a testing track, then promote it to production. First review of a new account's first app takes from a day to about a week. Here is each step with the details that matter.
1. Register as a developer
At play.google.com/console, pay the one-time $25 fee and verify your identity (ID document, sometimes a phone). Personal accounts created recently must run a closed test with at least 12 testers for 14 days before production access is granted — plan for that. Organisation accounts skip it but need a D-U-N-S number.
2. Test the APK on a real phone
In the builder, open Get your app and choose Try it on your phone. Scan the QR code, install the APK and use every screen. This is the same app Play will review.
3. Check the identity
Under Advanced settings in Get your app, check the App ID on Google Play (for example com.yourbusiness.appname). It is your app's permanent name on Play and is locked after the first build, so set it before you build. The version is shown at the top; the build number goes up by one on every build, as Play requires.
4. Back up your signing key
Every app is signed with your account's private key, created automatically on your first build. Every future update must be signed with the same key, so download a backup from Advanced settings → Your private key and keep it somewhere safe. Enrol in Play App Signing when Play asks — Google keeps the final key and your upload key can be reset if lost.
5. Build the app bundle
Choose Publish on Google Play in Get your app. In about three minutes you can download the signed .aab file. Play requires AAB, not APK, for new apps. The build is free.
6. Create the app in Play Console
Name, default language, app or game, free or paid (free cannot become paid later). Then the dashboard's setup checklist walks you through:
- Privacy policy URL — required. A short page saying what the app collects (often nothing) is enough; put it on any website you control.
- App access — if any part needs a login or PIN (an owner view), provide test credentials.
- Ads — declare honestly. Generated apps contain no ad SDK unless you add one.
- Content rating — a questionnaire; most business apps rate Everyone.
- Target audience — pick 18+ or 13+ unless the app is for children, which brings extra policy.
- Data safety — see below.
7. The data-safety form
Answer from the features you added and what the app actually does. Typical honest answers: a local-only tracker collects no data; an app that sends enquiries by WhatsApp does not itself collect data (the message leaves via another app); an app with a backend collects whatever the form fields are. Declaring more than you collect is as much a problem as declaring less — reviewers compare the form with the binary.
8. Store listing
- Title up to 30 characters; the real app name, with a keyword if it fits ("Fade Lab – Barber Booking").
- Short description 80 characters; the one-line promise.
- Full description up to 4,000; what it does, for whom, the key features, no keyword stuffing.
- Icon 512×512 PNG; feature graphic 1024×500; at least 2 phone screenshots, ideally 4–8 — take them from the running app.
9. Upload to a testing track
Testing → Closed testing → create a release, upload the AAB, add testers by email list. Share the opt-in link. Once the 14 days and 12 testers are met (personal accounts), apply for production access.
10. Production
Create a production release from the same bundle, choose countries, review the summary, roll out. New apps and updates are reviewed; expect one to seven days the first time and hours thereafter.
Rejections that catch first-timers
| Reason | Fix |
|---|---|
| Privacy policy missing or not reachable | Public URL, no login, mentions the app by name |
| Data safety does not match behaviour | Re-check every feature and form field in the app; correct the form |
| Login required, no test credentials | Provide them under App access |
| Broken functionality / blank screen | Install the APK on a real phone and test every screen before uploading |
| Misleading title or icon | No competitor names, no "official", no Google branding |
| Metadata: keyword-stuffed description | Write for humans |
After launch
Each year Play raises the required target SDK; build a new AAB in the builder and upload it. Updates are the same flow: make the change, raise the version in Get your app, build a new AAB (the build number goes up automatically), upload. About five minutes plus the build.