Google Play Target API level requirements for Android apps in 2025

Google Play regularly increases their Target API level requirement to ensure apps meet the highest security, performance, and compatibility standards.

Google Play Target API changes — Effective August 31, 2025

Google Play has a Target API level policy that requires apps to target recent Android versions to remain discoverable and installable, especially on newer devices.

Existing app compatibility: Starting August 31, 2025, existing apps — apps already published on Google Play — must target at least Android 14 (API level 34) to remain available to users on devices running Android 15 or 16.

New apps and app updates: Any new app submissions or updates to existing apps must target API level 35 to comply with Google Play’s latest Target API level requirement for apps.

Note: If your app targets a version lower than API level 34, it may not be visible or downloadable on devices running Android 15 or 16 via the Play Store.

Extension available: If you need more time to update your app, you can request an extension from August 31 to November 1, 2025. Also, note that you'll be able to access a form to apply for an extension for your app later this year in the Google Play Console.

Google’s API level: Exceptions

There are, however, exceptions to the Target API level requirements, including:

• Permanently private apps that are restricted to users in a specific organization and intended for internal distribution only

• Apps that target Android Automotive OS, or are packaged with APKs targeting Android Automotive OS

• Updates to Wear OS and Android TV apps, which can target Android 14 (API level 34) or higher

Tip: Choosing to develop your app using a leading platform like Median makes meeting ongoing app store requirements a breeze

How Median.co can help your apps stay complaint with Google Play’s Target API requirement

If your Android app is built with Median’s App Studio, you don’t need to worry about Google Play’s Target API updates because Median’s engineering team handles everything — from supporting the latest Android version to meeting Google’s compliance requirements.

Your app stays up to date and fully compatible with the latest devices, without you lifting a finger.

Here are three easy steps you can follow to keep your Android app built with Median compliant with Google Play’s latest API requirement:

1. Rebuild your app using Median’s App Studio and get the latest Android updates. The rebuild is only necessary if you have created an app before February 2025; apps that were rebuilt since February 2025 already target Android 16 (API level 36).

2. Test your app on Android 15. This ensures that all functionality, particularly permissions management, is working properly. You can beta test your Android app through Google’s very own Android Beta program as well.

   
   

   • Note that for most apps, Median’s browser-based simulators are sufficient; depending on the functionality of your app, a physical Android 15 device can be used.

3. Finally, publish an update to Google Play before August 31, 2025.

   
   

   • Median’s team of experts can take care of this on your behalf.

We are proud to announce our SOC 2 attestation, reinforcing our commitment to security and compliance!

How to comply with Google Play’s Target API level requirement without Median.co

If you decide to venture into this complex journey on your own, as an app developer, there are certain strategies you should follow to stay compliant with Google Play’s Target API level requirement.

You should review the behavior changes for apps targeting Android 15 or higher. Some of these include:

Core functionality

• Your app must declare at least one foreground service type; improper declarations can lead to background execution limits.

• BLUETOOTH_CONNECT permission remains strictly enforced, particularly for certain BluetoothAdapter methods.

• JobScheduler: Jobs must now return from onStartJob() or onStopJob() within a few seconds, or an ANR (Application Not Responding) will be triggered.

• ACCESS_NETWORK_STATE permission is mandatory for all uses of network constraints in jobs or work requests.

• Android 15 adds stronger background execution limits, especially targeting rarely used apps and broadcast delivery. Apps must use updated APIs or opt-in to user-initiated data transfers.

Privacy

• Users can now grant access to specific photos and videos rather than the entire media library.

• Read Media Visual/User Selected (Scoped Access) is enforced — apps targeting Android 15 should adopt the new user-selected media access permissions.

• Android 15 further limits visibility of installed apps unless explicitly required through QUERY_ALL_PACKAGES or package visibility configuration.

Security

• Implicit intents are only delivered to exported components, ensuring tighter control over inter-app communication.

• Dynamically loaded files (like DEX or native libraries) must be marked read-only before execution.

• Android 15 now blocks file path access to app internal files via content URIs—apps must use FileProvider or Storage Access Framework.

• Changes to pending intents: Apps must declare proper mutability (FLAG_IMMUTABLE or FLAG_MUTABLE) or face runtime exceptions.

User Experience and SDK Restrictions

• Full-screen intents are now restricted to specific use cases (e.g., calls or alarms), even more strictly enforced in Android 15.

• Non-SDK interfaces subject to version-based restrictions are further locked down—developers must adopt official SDK alternatives.

• Android 15 introduces predictive back gesture enforcement—apps should support the back-to-home animation preview using OnBackInvokedCallback.

These are just some of the behavior changes that are coming with Android 15 and higher. Learn more here.

Note: If you haven't updated your app since before Android 14, review the behavior changes for Android 14, or previous versions as required.

Finally, remember to implement all these required changes based on the functionality included in your app.

Want to know how it all works?

Get hands-on with Median’s comprehensive documentation, and build your app with ease.

View Documentation

Summary

Google Play’s annual increase to its API level requirement is here — after August 31, 2025, Google Play’s Target API level requirement has increased from API level 34 for Android 14 to API level 35 for Android 15.

Google increases its Target API level to ensure apps are compliant with the latest security, privacy, performance and compatibility requirements that come with new device and Android OS updates.

Extensions can be requested to extend to November 1, 2025.

To stay compliant, app developers must verify compatibility with AndroidX Library, update their third-party SDK dependencies, and adhere to specific behavior changes introduced in Android 14 and higher.

Median’s team of experts ensure your app built using our App Studio platform is compliant with Google Play’s latest API level requirement. Median does all the heavy lifting so that you don’t have to — making apps easier!

To learn more about this, book a call with our team of experts today!

Want to learn more about our plugins?

Launch a full-feature native app without native development!

Plugin library

Frequently asked questions

How do I check the Target API level of my current app?

You can check the Target API level of your app directly from the Google Play Console — it will be listed in your app’s details in the “App integrity” or “Advanced settings” sections.

You can also open the AndroidManifest.xml file in your app's source code. Within the file look for the targetSdkVersion attribute.

Why does Google Play increase their Target API level requirements?

Google Play increases their Target API level requirements to ensure a safe, secure, and smooth experience for users. Each new Android OS release brings security enhancements and functionality improvements.

By mandating app developers to update their apps and incorporate these changes, users can be assured that any app downloaded from Google Play is taking full advantage of the latest features offered by the Android platform and supported by their device.

Here’s a breakdown to why Google Play increases its Target API level requirements for Android apps annually:

• Security improvements: New Android versions often include important security updates. By requiring developers to target a more recent API level, Google confirms that apps integrate these enhanced security updates.

• Privacy enhancements: New Android releases come with new privacy controls and permissions management features that provide users more control over their data. With a higher Target API level, Google ensures that apps are compliant with the latest privacy standards.

• Better user experience: New APIs give developers the opportunity to evolve their apps to add new features and offer an improved UX across various Android devices

• Performance enhancements: Newer APIs offer improved resource management and higher performance across devices, making apps more user-friendly and responsive.

• Device compatibility: Android releases newer devices every year, with updated hardware and software, targeting the latest API level allows apps to maintain compatibility with the most recently released devices.

How can I stay compliant with Google Play’s current Target API level requirement?

To prepare your app for Android API level 35, follow these best practices:

• Check third-party SDK compatibility: Make sure all third-party SDKs used in your app fully support API level 35. If an SDK does not yet support this version, contact the SDK provider to address the issue and provide a compatible update.

• Target SDK version limitations: Be aware that setting a higher targetSdkVersion may restrict access to private Android platform APIs. Review and test your app for any potential issues caused by these restrictions.

• Verify AndroidX compatibility: Ensure that the version of AndroidX libraries you're using is compatible with both your app’s compileSdkVersion and targetSdkVersion. Incompatibility can lead to build errors or unexpected runtime behavior.

• Align versioning: The major version of the AndroidX libraries should match or be compatible with your app’s compileSdkVersion. If necessary, choose a targetSdkVersion that aligns with the supported version of AndroidX to avoid conflicts.

• Stay up to date: To take advantage of the latest features, security updates, and compatibility improvements, Google strongly recommends updating to the most recent stable release of AndroidX libraries.

I've uploaded an updated version of my Android app but the policy warning "App must target Android 15 (API level 35) or higher" is still displayed. How do I fix this?

If you upload a new Android app version targeting Android 15 (API level 35) to Google Play and still see a warning about an incorrect Target API level, it is often due to old APKs/AABs in testing tracks causing the issue. To fix this:

1. Log in to Google Play Console and select your app.

2. Go to the Release Management section (Production, Beta, Alpha, or Internal testing).

3. Check for warning messages and click on them to view details.

4. Identify old APKs/AABs causing the issue by clicking on "View affecting bundle."

5. Remove or deactivate these old bundles in the relevant track.

6. Upload your new release targeting API level 35.

7. Submit the new release for review.

This process ensures that there are no outdated bundles are causing the API level warning and you can then successfully release your updated app.

Why does Google update its Target API level requirements every year?

With new Android versions being released every year, security, privacy and performance features are constantly improving. By increasing their Target API level requirements for Android apps every year, Google ensures that apps downloaded by the end-users are safe, secure and are updated with the latest UX features.

How will existing users be impacted?

Existing users who have already downloaded your app from Google Play will not be impacted. They will still be able to discover, reinstall, and use the app on their Android devices (any Android OS version that their current app supports).

Will the latest API update impact app downloads?

New users on devices with newer Android OS versions may not be able to discover or even download your app from the Google Play Store, which will definitely impact your app download levels over time.

Can I update my existing app to stay compliant with Google Play’s API requirements?

With existing apps, you must target Android 14 which is API level 34 to ensure availability to new users on devices that run on Android OS higher than the app’s Target API level.

How can I make sure my new app is compliant with Google Play’s API update?

With new apps and any app updates, you must Target Android 15 (API level 35) or higher to be submitted and accepted by Google Play.

Are there any benefits to updating my app to target the latest API levels annually?

The main benefit of doing this annually is to ensure your apps benefit from the latest security enhancements, privacy controls, and performance improvements. All in all, staying compliant to the latest API level requirements ensures a better user experience, ensures compatibility with newer devices, and helps increase app visibility and downloads on Google Play, attributing to your overall app store optimization strategies for a Google Play listing.