Play target-API rules change over time. As of the November 2026 review, new and updated standard mobile apps generally need to target Android 16, API level 36 or higher under Google Play's August 31, 2026 policy.
Separate target from minimum SDK
The target API communicates the intended Android behaviour rules; minimum SDK controls the oldest Android version on which an app may run.
Check affected app categories
Wear OS, Android TV, Android Automotive and other specialised categories may have different requirements. Review the official support table for the product type.
Practical lens: The best decision depends on users, the existing business system, data risk and the outcome the app needs to deliver. Validate these conditions before committing to features.
Budget compatibility work
Moving to a newer target can affect permissions, behaviour changes, libraries and test requirements. A manifest edit alone is not a safe migration plan.
Check before submission
Policy pages can change. Verify current requirements in Play Console and Google's published support documentation close to release.
Example from a business workflow
An existing app with old permissions may require code and UX changes when moving to API level 36, even if the old build worked on developers' devices.
Questions to take into your project discussion
Turn the guidance into a brief by confirming each of these items with the people responsible for the product:
- Target SDK requirement
- Platform-specific exceptions
- Library and behaviour tests
- Play Console verification
What to do next
Write a one-page summary of your user groups, current workflow, necessary integrations and decisions still open. Evaluate trade-offs against those facts. For an Android-specific requirement, Archeet Infotech can discuss the implementation scope; work such as specialist SEO or hosting belongs with the relevant group concern.
These official resources explain relevant Android and platform practices. Project-specific decisions require verification at implementation time.