Google Play · target API 36 · 16 KB
Update target API level to 36 and keep your app on Google Play
The API 36 extension runs until 1 November 2026
Got a Play Console warning, a rejected update, or an app new users can no longer find? We bump the target API to 36, update Gradle and libraries, make native code 16 KB-ready and hand you a signed AAB with a change log.
- Senior Android developer, direct
- Fixed price after the audit
- Signed AAB and a change report
Audit from $150 · update from $390
In short
What is target API level and why Google Play requires it
Target API level (targetSdk) is the Android version whose rules your app is built for. Google Play raises the minimum every year, so apps keep up with new security, privacy and UI requirements. Since 31 August 2026, new apps and app updates must target Android 16 (API 36).
Deadlines
Google Play deadlines 2026–2027: what applies now and what’s next
Statuses are calculated for today; dates come from the official Android developer pages.
Source: developer.android.com, checked 3 October 2026
- In force
Apps must target Android 16
New apps and app updates must target API 36. Existing apps below API 35 are unavailable to new users on devices running newer Android versions.
- Next up
Extension ends
An extension requested in Play Console runs until 1 November 2026. After that, updates without API 36 won’t go through.
- Planned
16 KB for native code
Updates of apps with C/C++, native SDKs or some cross-platform frameworks can’t be released without 16 KB memory page support.
- Planned
Developer verification goes global
Enforced since 30 September 2026 in Brazil, Indonesia, Singapore and Thailand. In 2027 it expands to all certified Android devices.
- Expected
Next target API bump
The requirement usually rises every year at the end of August, but Google hasn’t announced the 2027 one yet. At API 37, the temporary opt-outs for predictive back and large-screen orientation stop working.
Self-check
Does your app meet Google Play requirements?
Three answers show what affects your app, by which dates, and how much work it is.
Target API 36Not compliant
Updates are blocked since 31 Aug 2026 (with an extension, from 1 Nov 2026). Below API 35 the app is unavailable to new users on newer Android.
16 KB page sizeNeeds a check
We’ll check in the audit by looking for .so files in the AAB. If there are any, 16 KB support is due by 1 Feb 2027.
Edge-to-edge & backNeeds work
At API 36 you can’t opt out of edge-to-edge, and predictive back is on by default: onBackPressed is no longer called.
Dates for your app
- 31 Aug 2026API 36in force
- 1 Nov 2026extension endsin force
- 1 Feb 202716 KBin force
- ~Aug 2027API 37, expectedin force
Scope
2–5 working days
An estimate, not a quote: the exact date and price are fixed after the audit.
Price
Update — from $390
the $150 audit is credited to the update
Common situations
Play Console warning, rejected update or app removed from Google Play? Here’s the fix
What you see in Play Console — and the help you get with each warning or Google Play policy violation.
- Warning
App must target Android 16 (API level 36) or higher
Your app must target Android 16
What we doWe bump targetSdk to 36, work through the Android 14–16 changes that affect your code and ship the update.
- Rejected
Update rejected
The update was rejected in review
What we doWe read the reason in Play Console, fix the code, permission declarations or Data safety form, and resubmit.
- Removed
App removed · unavailable for new users
Policy violation: app removed or hidden
What we doWe find the cause — an outdated target API or a policy issue — fix it and, if needed, draft the appeal. Google makes the appeal decision.
- 16 KB
…must support 16 KB memory page sizes
The 16 KB page size warning
What we doWe update the NDK, native SDKs and framework, rebuild .so files with 16 KB alignment and test on a 16 KB emulator.
What’s included
What’s included when we update your Android app for Google Play
More than a new number in build.gradle — and you get a report of exactly what changed.
targetSdk and compileSdk 36
We work through the Android 14, 15 and 16 behavior changes that affect your code.
Gradle, AGP, Kotlin, dependencies
Build tooling and libraries updated; abandoned ones replaced.
Edge-to-edge
Content no longer hides under the status and navigation bars.
Predictive back
Back handling moved from onBackPressed to OnBackPressedCallback.
Foreground service types
Types and permissions declared, so services don’t crash.
16 KB for .so libraries
Alignment checked, native code and SDKs rebuilt.
Testing on Android 16
Key flows on emulators and the Play Console pre-launch report.
Signed AAB
Built with your upload key — or you sign it yourself.
Release notes
“What’s new” text for your store listing.
Data safety form
Matched to your real SDKs and permissions, so the release isn’t rejected.
16 KB page size
Google Play 16 KB page size: who needs a fix before 1 Feb 2027
New Android devices are moving from 4 KB to 16 KB memory pages. Native libraries built for 4 KB may not work correctly on them. That’s why, from 1 February 2027, Google Play won’t accept updates without 16 KB support.
Who it affects
- apps with C/C++ or NDK code
- apps with third-party native SDKs
- Flutter, React Native, Unity and app builders that bundle native libraries
The 16 KB page size fix
We find every .so in the build, check alignment, update the NDK, build plugin and SDKs, then rebuild and test on a 16 KB emulator. Java/Kotlin-only code is already compatible — in that case we simply confirm it.
Who it’s for
Update your Android app for Google Play — even without an in-house developer
Owners whose developer left
The app works, but nobody can update it. We take over the code, update it and leave notes for next year.
Agencies and studios
We update client apps under your brand, in your repository — fixed price, fixed date, a report you can forward. See white-label for agencies.
Cross-platform and app builders
Flutter, React Native, Unity, Cordova, Capacitor — or an app builder that exports the project. If it doesn’t, you’ll hear it in the audit.
What we need from you
Three kinds of access — and your keys stay safe
No passwords to your Google account, ever.
Code
Repository access (GitHub, GitLab, Bitbucket) or a project archive. Only an AAB/APK, or the developer is gone? We start with an audit and tell you what’s possible without source code.
Play Console
Invite us as a user with release permissions only — no financial data, no password sharing.
Signing
With Play App Signing, Google keeps your app signing key — we never see or ask for it. The upload key is enough for a release, or you upload the signed AAB yourself.
Myrado Studio is an independent studio. We’re not affiliated with Google and don’t influence Google Play review decisions.
Pricing
Google Play target API level update service: pricing
A target API level 36 update at a fixed price after the audit — no hourly billing.
Audit
from $150
credited to the update
- What breaks at API 36 and 16 KB
- Outdated libraries and SDKs
- A fixed price and date for the update
- 1–2 working days (estimate)
- API 36 + 16 KB
Full update
from $390
price fixed after the audit
- Everything in “What’s included”
- Signed AAB and change report
- Help with publishing in Play Console
- Rejected because of our changes? Fixed free
Yearly compliance plan
from $490/year
so next August isn’t another fire drill
- Next year’s target API bump
- Play Console warnings and emails handled
- Data safety and library updates
- Priority in the queue
Why a yearly plan beats a one-off fix
The requirement rises every year: the next bump is expected around the end of August 2027, though Google hasn’t announced it yet. At API 37 the temporary opt-outs for predictive back and orientation stop working, so next year’s update will be bigger. With the plan we prepare early — and once the code is healthy, you can add an AI voice assistant to the app.
If Google rejects the update because of our changes, we fix it free of charge.
FAQ
Questions about updating your app for Google Play
Didn’t find your answer? Ask in the form — the developer replies.
How much does a target API 36 update cost?
The audit is from $150 and is credited to the update. A full update is from $390, and the yearly compliance plan from $490 per year. The final price is fixed after the audit: it depends on the stack, how outdated the libraries are and whether there is native code.
How long does the update take?
The audit takes 1–2 working days. Updating a native Kotlin/Java app from targetSdk 34–35 usually takes 1–4 working days; Flutter, React Native, Unity or a jump from API 33 or lower take longer. These are estimates — we give an exact date after the audit.
What access do you need?
The repository or a code archive, a Play Console invitation with release permissions, and a clear picture of how the app is signed. We never need your Google account password. If there’s no source code, only an AAB or APK, we start with an audit and tell you what’s realistic.
What if Google rejects the update?
If Google rejects the update because of our changes, we fix it free of charge. If the reason is something else — the store listing, content policy, an older violation — we explain what happened and propose a plan with a price before any work starts.
Is my app signing key safe?
We don’t ask for the app signing key: with Play App Signing, Google keeps it, and the upload key is enough for a release. Or we hand you a ready AAB and you sign and upload it yourself. If the upload key is lost, the account owner can request a reset in Play Console.
Do you update Flutter and React Native apps?
Yes — Flutter, React Native, Unity, Cordova, Capacitor and Ionic, as well as native Kotlin and Java. For cross-platform apps we update the framework, plugins and native libraries for 16 KB. App-builder apps work if the builder exports the project or supports API 36 itself.
What happens after 1 November 2026?
The extension ends and Google Play won’t accept updates that don’t target API 36. Existing users keep the app, but if it targets below API 35, new users on newer Android devices can’t find it. You can still ship an API 36 update after that date — there’s just no more room to wait.
Does Android developer verification affect me?
It’s enforced since 30 September 2026 in Brazil, Indonesia, Singapore and Thailand and expands to all certified Android devices in 2027. Google Play developers complete it through Play Console. It matters most for apps installed outside Google Play, such as enterprise APKs. We’ll tell you what to do during the audit.
Get started
Send your app for a check
Tell us what happened — the developer replies with what needs doing, what it costs and when it’ll be ready.
- A reply with first questions within one business hour
- Audit: 1–2 working days (estimate), then a fixed price and date
- Update, tests, a signed AAB and a change report
Speeds up the estimate: your Google Play link and a screenshot of the Play Console email or warning.
Development
More development services
- MCP server developmentConnect Claude, ChatGPT or Cursor to your CRM, accounting and databases — with scoped access and an audit log.
- Telegram Mini App developmentA shop, booking or loyalty app inside Telegram, with an AI agent in the same bot.
- Lovable developer: fix & launchSecurity audit and launch sprint for apps built with Lovable, Bolt, Replit, Base44 and Cursor.
- PRRO & Checkbox integration (Ukraine)Automatic fiscal receipts for selling in Ukraine: card payments, cash on delivery, refunds.
Also from the studio