Google Play Target API 2026: 5 Easy Steps to Update Your App

Google Play target API guide: a smartphone with an app update arrow and API level 36 badge (TechBella Solutions)

If your business has an Android app on Google Play, a quiet deadline may already have changed what you can publish. Google Play requires new apps and app updates to target a recent Android version, and the rule for 2026 raised the bar to Android 16, API level 36.

This Google Play target API guide explains the current requirement, who it affects and how to update without breaking your app. We follow Google’s official Android developer documentation, which is dated 16 October 2026, so check it for the latest details. It is written for business owners as well as developers.

App typeTarget API level required (from 31 Aug 2026)
New apps and updates (phone and tablet)Android 16 (API 36) or higher
Wear OS and Android Automotive OSAndroid 15 (API 35) or higher
Android TV and Android XRAndroid 14 (API 34) or higher
Existing apps (to stay available to new users on newer Android)Android 15 (API 35) or higher
Source: Google Android Developers target API level requirements. Confirm current dates in Play Console.

What the Google Play target API requirement says

According to Google’s target API level documentation, from 31 August 2026:

  • New apps and updates must target Android 16 (API level 36) or higher to be submitted to Google Play. Wear OS and Android Automotive OS apps must target Android 15 (API level 35) or higher, and Android TV and Android XR apps must target Android 14 (API level 34) or higher.
  • Existing apps must target Android 15 (API level 35) or higher to remain available to new users on devices running newer versions of Android.
  • Extension: developers could request an extension to 1 November 2026.
  • Exemption: permanently private apps restricted to a specific organisation for internal use.

The documentation page also shows a “last updated” date after the 31 August start, so confirm the current dates and the extension process in Play Console before you plan around them.

What happens if you do not comply

Google’s wording is that out-of-date apps are unavailable to new users of devices that run newer versions of Android. Apps that target Android 14 (API 34) or lower will only be available on devices running the same or an older Android version than their target.

Existing users on a device keep access. The damage is gradual: new customers on new phones cannot find or install your app, so growth quietly stalls.

Targeting is not the same as supporting

Setting targetSdk does not drop support for older phones, since that is controlled by the minimum SDK. Target level tells Android which platform behaviours your app was tested against. Raising it can change permissions, background work, notifications, storage access and screen behaviour, so it needs testing.

What counts as a behaviour change

Each Android version changes how apps behave, and Google publishes the details as behaviour changes. They fall into familiar groups. Permissions and privacy rules may become stricter. Notifications may need new approvals. Background work such as services, alarms and jobs may be limited more tightly. Screen and layout rules may change for tablets, foldables and different window sizes. File and media access can move to newer, narrower models.

Your developer does not need to memorise all of it. They need to read the changes for each version between your current target and the new one, search the codebase for the affected features, and test them. That is why we suggest an audit first: a list of the affected features is the basis for an honest estimate.

Five steps to update your target API

Step 1: Check what your app targets today

Open your Gradle configuration, where targetSdk is set in the defaultConfig block, or the manifest’s <uses-sdk> element. Also check Play Console for warnings.

Step 2: Read the behaviour changes

Google publishes behaviour changes for each Android version. Read the changes for every version between your current target and API 36, since they apply cumulatively.

Step 3: Update libraries and build tools

Old libraries often block a higher target. Update the Android Gradle plugin, Kotlin and key dependencies, and replace any that are no longer maintained.

Step 4: Test on real devices and emulators

Test installation, sign-in, push notifications, payments, camera and location permissions, deep links and background tasks on Android 16 devices and older ones. Test tablets and foldables if you support them.

Step 5: Release gradually

Use staged rollouts in Play Console, watch crash reports and ratings, and keep the ability to halt the rollout.

A sample six-week plan

For a typical business app, a plan like this keeps work calm and visible:

  1. Week 1: audit the current target, libraries, build tools and Play Console warnings, then write the list of risks.
  2. Week 2: update the build tools and dependencies on a branch and fix compile errors.
  3. Weeks 3 and 4: raise the target API, work through behaviour changes and fix issues one feature at a time.
  4. Week 5: test on real devices, including an older phone and a recent one, and run through sign-in, payments, notifications and permissions.
  5. Week 6: release to a small percentage of users, watch crash reports and ratings, and increase gradually.

Short apps may take less time and complex ones more. The point is to have a plan, an owner and dates.

Problems teams usually run into

Raising the target API tends to expose old code. From our experience of app maintenance, the usual suspects are libraries that have not been updated for years, permission flows written for older Android versions, background work that the system now limits, and layouts that assume a fixed screen size. None of these is exotic, but each needs a person to read the platform’s behaviour changes and test on real devices.

Treat the update as maintenance with a budget and a calendar, not a surprise. A small update done every year is usually cheaper and safer than a big one forced by a deadline, because each step is small and the app never falls far behind.

What to do if your app is already out of date

Do not panic, and do not rush an untested release. First, check Play Console for warnings and the extension option if it is still available. Then ask your developer for an estimate that covers library updates, testing and a staged rollout. If the original developers are gone, a new team can audit the code and tell you what is needed. Keep a record of your signing keys and Play Console access, because without them nobody can publish an update.

Native, hybrid or web app: how does the rule apply?

The target API requirement applies to apps you publish on Google Play, whatever technology built them. Native Kotlin or Java apps set the target directly. Hybrid and cross-platform apps built with frameworks still produce an Android package with a target level, usually set through the framework’s configuration, and the framework version may limit how high it can go. A trusted web app packaged for Play follows the same store rules.

If your app was built with a cross-platform framework, ask your developers which framework version it uses and whether that version supports the new target. Sometimes the framework itself needs to be upgraded first, which affects the schedule. A plain website does not need to meet this rule unless you also publish it as an app.

What business owners should ask their app team

  • Which target API level does our app use today?
  • When did we last update dependencies?
  • Do we have automated tests, or a device test plan?
  • What is the plan for next year’s requirement?
  • Is anyone watching Play Console warnings and emails?

Planning ahead

One search result suggests the next annual step would be API 37, but Google’s page does not state a date for it, so treat that as unconfirmed. The pattern is clear, though: Google raises the bar every year. Build a yearly review into your app maintenance plan, ideally with a budget, so the update never becomes an emergency.

Our Android development team can audit your target level and carry out the upgrade, and our website maintenance approach applies the same yearly review to sites.

Keeping your Play Console account healthy

A few housekeeping tasks prevent painful surprises. Make sure the contact email on the account is monitored by a person, not a former employee. Keep at least two owners with access, and store your app signing and upload keys safely. Read policy emails from Google promptly, because they often carry deadlines. Note the date of the next requirement change in your calendar, and review your privacy policy and data safety form whenever the app starts collecting new information.

These tasks take minutes a quarter. They matter because a lost account or an ignored warning can stop your app updates entirely, long after any target API deadline.

Communicating with users during an update

An update that raises the target level may change how your app behaves, so tell users when something visible changes. Write release notes in plain language, mention new permission prompts and explain why they are needed. If notifications or background features behave differently on newer Android versions, add a short help article and brief your support team before the release.

Watch ratings and reviews for the first week and reply promptly to complaints. A quick, polite answer often turns a frustrated user into a loyal one, and the feedback shows issues that testing missed.

Is your Android app up to date for Google Play?

We can audit your target API level, update libraries and test your app on current Android versions before Google Play blocks new installs.

See Android development

Frequently Asked Questions

What target API level does Google Play require in 2026?

From 31 August 2026, new apps and updates must target Android 16 (API level 36) or higher, with different minimums for Wear OS, Automotive OS, TV and XR. Existing apps need API 35 or higher to stay available to new users on newer Android versions.

Will my app be removed from Google Play if I miss it?

Google says out-of-date apps become unavailable to new users on devices running newer Android versions. Existing users keep access, but new installs from those devices stop.

Does raising the target API drop support for old phones?

No. Minimum SDK controls which devices can install the app. Target SDK affects the platform behaviours the app opts into, so test carefully.

Share This Article:

Start a project

Having a project idea in mind?

Tell us what you are building. A few lines about your goals are enough to start.

  • What you want to achieve
  • Your current website or setup
  • Deadlines and a rough budget