1. Developer account
Register at Google Play Console with a one-time fee and complete identity verification. New personal accounts must run a closed test with a minimum number of testers for a set period before they can publish to production — check the current requirement in Play Console when you register, and plan for it.
2. Build an AAB you can update
- Google Play requires an AAB for new apps.
- Sign it with an upload key you keep. Every future update must be signed with the same key — see app signing explained.
- Use a final package name; it cannot change after publishing.
- Increase the version code for every upload.
With APK Maker, AAB output and your own signing key are part of Pro.
3. Store listing
| Item | Limit / size |
|---|---|
| App name | Up to 30 characters |
| Short description | Up to 80 characters |
| Full description | Up to 4,000 characters |
| App icon | 512 × 512 PNG |
| Feature graphic | 1024 × 500 JPEG or 24-bit PNG |
| Phone screenshots | At least 2, JPEG or 24-bit PNG |
4. Policy forms
- Privacy policy — a public URL, required for most apps.
- Data safety — what data the app and its SDKs collect and share. For a website app, include what your website collects.
- Content rating questionnaire and target audience.
- App access — give reviewers a test login if parts of the app need one.
5. Test, then release
Upload the AAB to internal or closed testing first, install it from the testing link, and check it on a real phone. Then promote the release to production and add release notes — format them for every language with the Play release notes formatter. Reviews often take a few days for new apps.
Avoid common rejections
- Minimum functionality: a website wrapper with nothing extra can be rejected; add push notifications, native navigation and offline handling.
- Broken pages or login walls without reviewer credentials.
- Metadata: no keyword stuffing, no other brands' names or logos.
After launch
Share a tracked install link built with the Play referrer link builder so you can see which channels bring installs.
A realistic timeline
| Stage | What happens | Typical time |
|---|---|---|
| Account | Registration and identity verification | A day to a few days |
| Preparation | AAB, listing text, icon, feature graphic, screenshots, privacy policy | An afternoon |
| Testing | Internal test, then closed test if your account type requires it | From same day to a couple of weeks |
| Review | Production release reviewed by Google | Often a few days for new apps |
Checklist before you press "Send for review"
- Package name is final and not
com.example.*. - Version code is higher than any previous upload.
- Upload key backed up in two places.
- The app opens to useful content on a fresh install, with no login wall — or reviewer credentials are provided.
- Privacy policy URL loads and mentions the data your website and app collect.
- Screenshots show the real app, not mock-ups of features it doesn't have.
- Data safety answers match your privacy policy.
- Release notes written — use the release notes formatter.
Publishing updates
For each update: build a new AAB with the same package name and upload key, increase the version code, upload it to a new release, add release notes, and roll it out — optionally to a percentage of users first with a staged rollout.
Make your APK now — free
No Android Studio, no code, no watermark. Pick what you are starting from:
Frequently asked questions
Can I publish a free APK from APK Maker on Google Play?
Google Play needs an AAB signed with a key you control, which comes with Pro. Free APKs are for direct installs and sharing.
How long does Google Play review take?
Often a few days for a new app; updates are usually faster. Times vary and can be longer for new developer accounts.
Do I need a privacy policy for a simple app?
In most cases yes — Play requires a privacy policy URL for apps that handle personal or sensitive data, and a website app usually does.