Google Play target API level: what it means and what to do
Last reviewed 21 November 2026
Each year Google raises the Android version apps must be built for. Miss it, and you can’t publish updates. Fall further behind, and new users on newer phones can’t find your app. It’s a technical setting, but the consequences are commercial, so here’s what a founder needs to know.
Since 31 August 2026, new apps and updates on Google Play must target Android 16 (API level 36), with lower levels for watch, TV, car and XR apps. Apps already on the store must target at least Android 15 (API 35) to stay visible to new users on newer phones. Ask your developer to update the target, test the behaviour changes it brings, and plan for this every year.
What “target API level” means
Every Android app declares which Android version it was built and tested for. That’s the target. It doesn’t stop the app running on older phones: those are set by a separate minimum. But many Android changes only switch on when an app targets the newer version, which is why Google makes everyone move up.
The rules today
From Google’s target API page:
- New apps and updates must target Android 16 (API 36) since 31 August 2026.
- Wear OS and Android Automotive apps need API 35, and Android TV and Android XR apps need API 34.
- Apps already published must target at least Android 15 (API 35) to stay available to new users on newer Android versions.
- An extension to 1 November 2026 was available through a warning on the Policy status page. That date has now passed.
What happens if your app falls behind
There are two separate limits. Below Android 16 (API 36), you can’t ship any update, even an urgent fix, until the target is raised. Below Android 15 (API 35), new users on newer phones also can’t find or install the app, because Google only offers it to devices running the same or an older Android version than its target, and Google warns that downloads may drop. People who already installed it keep it either way.
What changes with Android 16
Raising the target isn’t just a number change. Android 16’s changes include screens that always run edge to edge, the new back gesture animation, and on tablets and foldables, apps can no longer lock the orientation or stop resizing. Each can make screens look wrong if nobody tests them.
If your app is built with React Native, Flutter or Capacitor
- React Native 0.81 and Expo SDK 54 target Android 16 by default.
- Capacitor 8 sets the target to 36. Capacitor 7 used 35.
- Flutter manages the target through its own tooling, and teams can also set it directly.
So for many apps the fix is upgrading the framework, which can bring its own changes. That’s why it belongs in your maintenance plan, not left for the week of the deadline. See what app maintenance involves.
What to ask your developer
- What does the app target today, and does it meet the current rule?
- What needs upgrading to reach it: the framework, libraries, or our own code?
- Have the Android 16 changes been tested, including on a tablet?
- When is next year’s deadline, and is it in the plan?
Questions founders ask
Will my app stop working for existing users?
No. People who already installed it keep it. Below API 36 you can’t publish updates, and below API 35 new users on newer phones can’t find or install it.
Does targeting Android 16 drop support for older phones?
No. The oldest Android version an app supports is a separate setting. Targeting a recent version still lets the app run on older ones.
Does this happen every year?
Yes. Google raises the requirement regularly, so plan an update each year rather than waiting for the warning.