- Yearly
- Target API rebuild
- Always
- Back up the keystore
- Every release
- Higher versionCode
- Automatic
- WebView engine updates
What updates on its own
- Your content — every page, product and post, instantly.
- The WebView engine — Google updates Android System WebView through the Play Store roughly monthly, bringing security fixes and new web features.
What needs a new build
| Change | Rebuild? |
|---|---|
| Website content, design, new pages | No |
| App name, icon, splash, colours | Yes |
| Start URL, tabs, link rules | Yes |
| New permission (camera, location, notifications) | Yes |
| Google Play target API deadline | Yes, yearly |
The yearly API deadline
Each August Google Play requires app updates to target a recent Android version. Apps that fall behind can't publish updates and, over time, become hidden from users on newer devices. Rebuilding with an up-to-date converter usually handles it — plan it into your calendar.
Release checklist
- Same package name, same signing key.
- Version code higher than the last release.
- Install over the previous version on a test phone — data and login should survive.
- Upload the AAB to an internal or closed track first, then production.
- Write release notes users understand.
Keep the keys safe
Store the keystore file and its passwords in a password manager and an offline backup. If you use Play App Signing, Google keeps the app signing key and you can reset a lost upload key — but sideloaded APK users still depend on yours.
Frequently asked
How often should I update my converted app?
At least once a year for the API deadline, plus whenever you change app-level features. Content changes need no update.
What if I lose my signing key?
With Play App Signing you can request an upload key reset. Without it, you can't update the existing app and would have to publish a new one.