Free HTML to Publish on Google Play
From your phone to the Play Store. This is the path that works for apps built with Free HTML to APK, including the closed test that new personal developer accounts must run.
1. Prepare your app in the builder
- Package name: choose your own, for example
com.yourname.yourapp. You can never change it after publishing. - Version: every upload needs a higher version code. Leave Auto-increase version code on.
- Permissions: turn on only what your app uses. Every permission has to be justified in Play Console.
- Output: choose APK + AAB. Google Play only accepts the AAB.
2. Keep your key safe
Your app is signed with a key stored on your phone. Open Signing keys and tap Back up; the backup goes to Downloads/FreeHtmlToApk. Copy it somewhere safe, such as a cloud drive. Updates must be signed with the same key.
3. Create the app in Play Console
- Sign up for a Google Play developer account (one-time fee charged by Google).
- Create app: name, default language, app or game, free or paid.
- Complete the App content section: privacy policy, ads, app access, content rating, target audience, Data safety.
- Fill in the store listing: short and full description, icon (512 × 512), feature graphic (1024 × 500) and at least two phone screenshots.
4. Privacy policy and Data safety
Google requires a public privacy policy URL for most apps, and always if you use sensitive permissions such as camera, location or contacts. Describe what your app collects. The builder itself adds no analytics or tracking to your app; if you turn on AdMob, declare advertising data as Google's documentation describes.
5. Run the closed test (new personal accounts)
Personal developer accounts created after November 2023 must run a closed test with at least 12 testers who stay opted in for 14 days in a row before production access is granted.
- In Play Console, open Testing → Closed testing, create a track and upload your AAB.
- Add testers by email or with a Google Group, and share the opt-in link.
- Testers join, install your app from Google Play and keep it installed.
- After 14 days, apply for production access from the Dashboard and answer Google's questions about your test.
More about the rule: 12 testers for 14 days, explained.
Need 12 testers for Google Play?
Partner adNew personal Google Play accounts must run a closed test with at least 12 testers for 14 days in a row before the app can go live. Closed Test Pro connects you with testers, so you can get through it without asking friends.
- 12 testers for 14 days, with a free plan
- Testers on real phones, not emulators
- Daily reminders keep testers active
- Testers who drop out are replaced
6. Release to production
Create a production release, upload the AAB, add release notes and send it for review. Reviews usually take from a few hours to a few days.
7. Ship updates
- Change your files or settings in the builder and build again; the version code goes up automatically.
- Upload the new AAB as a new release on the same track.
- Always build with the same signing key.
Common rejection reasons
| Problem | Fix |
|---|---|
| Minimal functionality: the app is only a website wrapper | Add app-like value: offline content, native features from the JavaScript API, menus and a real home screen. |
| Missing or broken privacy policy | Host a policy at a public URL and link it in Play Console and inside the app. |
| Permissions not justified | Turn off permissions you don't use, and explain the ones you do. |
| Impersonation or copyright | Only package content you own or are authorised to use, under your own name and brand. |