Why the target API keeps rising
targetSdkVersion declares which Android version an app is adapted to. To give users newer security and privacy protections, Google Play periodically raises the minimum target API for new apps and updates, usually with a deadline around the end of August each year.
Exact numbers change annually, so check Google's current target API requirement page rather than relying on a fixed version here. Console also warns at upload time if the build falls short.
What happens if you fall behind
- New apps are rejected at upload and cannot enter any track
- Existing apps cannot publish updates after the deadline; installed users keep working but visibility on new devices may drop
- Long-neglected apps targeting an old API may become hidden from new users on recent Android versions
- Extensions can be requested with a reason but are not guaranteed
Buyers of accounts with legacy apps should note that an app with no recent updates is probably already below the bar, so the first release after handover can be blocked.
Also useful in this topic cluster:
Other build requirements that affect publishing
| Requirement | Detail | How to check |
|---|---|---|
| AAB format | New apps upload as Android App Bundles | Use bundleRelease in Gradle |
| Play App Signing | New apps publish with Play App Signing | Register on first upload |
| 64-bit | Apps with native code need 64-bit builds | Check abiFilters and .so files |
| Target API | Meet the current floor | Read targetSdk in build.gradle |
| Permissions | Sensitive permissions need justification | Match permissions to features |
Raising targetSdk is more than editing a number: test behaviour changes such as background limits, notification permission, media access and foreground service types. Reserve a few days for regression.
Package name (application ID) rules
The package name uniquely identifies the app on Google Play, for example com.example.app. It needs at least two segments, starts with a letter and uses letters, digits and underscores separated by dots. Most important: once published it cannot be changed; a new name means a brand-new app with no migration of users, ratings or stats.
A package name is unique across Play and cannot be reused if taken; deleting an app does not release it. Avoid example prefixes and use a reversed domain you own or your brand.
// app/build.gradle (example; follow the current Google Play target API rule)
android {
namespace "com.example.notes"
defaultConfig {
applicationId "com.example.notes" // permanent once published
minSdk 24
targetSdk 35 // raise when the yearly rule changes
versionCode 1
versionName "1.0.0"
}
}Package names and account ownership
A package name created in an account stays bound to it. If account ownership changes, the name moves with the account; with an app transfer, it moves with the app subject to signing and account-status requirements. When buying, list every app's package name, signing method and whether an upload key exists.
If you want a package name already used in someone else's account, they must transfer the app officially — you cannot simply re-register it. See the comparison of account transfer versus app transfer.
Pre-first-release freeze checklist
- Decide the package name; avoid example domains and third-party brands
- Confirm targetSdk meets the current floor and regression-test
- Build the AAB and verify 64-bit libraries
- Confirm signing: Play App Signing with an upload key you keep
- Upload once to the internal track early so warnings surface
These checks take little time and prevent a blocked first release.
Related reading:
Related
Related desks