On this page · 11 sections
- What Google has published, and what it has not
- The annual pattern behind 31 August
- What 2027 will probably look like
- Form-factor floors: Wear OS, TV, Automotive, XR and Android Auto
- The Android 17 changes that fire at targetSdk 37
- Minor SDK releases: why 37.1 and 37.2 do not move your target
- Extension requests: how they worked in 2026
- A dated checklist working back from August 2027
- Notes for Indian teams and agencies
- How eCorpIT can help
- References
Summary. Google has named the month but not the day. In a 13 February 2026 Android Developers Blog post, Google said Play will require new apps and updates to target API level 37 in August 2027. The Play Console Help page that carries the formal rule, read on 7 November 2026, still lists only API 35 from 31 August 2025 and API 36 from 31 August 2026, with extensions to 1 November 2026. Google's Play Billing Library table already uses 31 August 2027 and 1 November 2027 for its next deadline, so plan for 31 August 2027. The extension window, the existing-app threshold and the Wear OS, TV, Automotive and XR floors are still unpublished. Android 17 (API 37) shipped on 16 June 2026, and Google says its Q2 release is the only one with planned app-breaking changes, so API 37.1 and 37.2 add no target work. Google's page for apps targeting Android 17, last updated 31 October 2026, lists 17 changes, from a three-hour SMS OTP delay to the end of the large-screen opt-out. Ship a target-37 build to production by June 2027 and keep July as buffer.
About this article. For Android leads, product owners and agencies shipping on Google Play, with notes for Indian teams. We checked every date, API level and behaviour change against Google's own pages (Play Console Help, developer.android.com and the Android Developers Blog) and archived copies of them, using the versions served on 7 November 2026. This is general information, not legal advice; Google can change Play requirements at any time, and no vendor paid for inclusion. Researched with AI assistance and reviewed by our editorial team.
What Google has published, and what it has not
Here is what Google had stated by 7 November 2026, and what is still missing.
| Item | Status on 7 November 2026 | Where it comes from |
|---|---|---|
| Play will require new apps and updates to target API 37 in August 2027 | Stated by Google, month only | Android Developers Blog, 13 February 2026 |
| The exact day in August 2027 | Not published | 31 August in 2025 and 2026 |
| An extension window | Not published | 1 November in 2026 |
| The level existing apps need to stay available to new users | Not published | One level below the new-app floor in 2026 (API 35) |
| Floors for Wear OS, Android Automotive OS, Android TV and Android XR | Not published | Each had its own lower floor in 2026 |
| Android 17 behaviour changes for apps targeting API 37 | Published | Android Developers, last updated 31 October 2026 |
Our August 2026 guide to the Android 17 changes said the Play page set no API 37 date. That is still true of the Play page, but Google's February post had already named August 2027.
The annual pattern behind 31 August
Google's Play Help page keeps the last two requirements on record; the table copies it.
| Requirement | Phones, tablets, foldables (new apps and updates) | Wear OS | Android Automotive OS | Android TV | Android XR | Extension |
|---|---|---|---|---|---|---|
| 31 August 2025 | API 35 (Android 15) | API 34 | API 34 | API 34 | Not listed | Not shown on the current page |
| 31 August 2026 | API 36 (Android 16) | API 35 | API 35 | API 34 (unchanged) | API 34 | To 1 November 2026 |
| August 2027 | API 37 (Android 17), per Google's blog | Not published | Not published | Not published | Not published | Not published |
The formal text arrives late: archived copies show the Play Help page still carried the 2025 rule on 19 June 2026 and the API 36 rule by 18 July, six to ten weeks before the deadline. Expect the 2027 table around mid-2027, not now.
Three rules from Google's page apply every year.
- Submissions. After the date, Play Console rejects a new app or update that targets below the floor. Any new version submitted for review to replace a live app counts as an update.
- Availability. Existing apps below a second, lower threshold are shown only on devices whose Android version is no newer than the app's target. Users who already installed the app keep it and can reinstall it.
- Exceptions. Permanently private apps, limited to users in one organisation and distributed internally, are exempt.
What 2027 will probably look like
This is our reading of the pattern; the confidence column is editorial judgement.
| Item | Projection for 2027 | Basis | Confidence |
|---|---|---|---|
| Phone and tablet floor for new apps and updates | API 37 | Google's 13 February 2026 blog post | High for the level and month |
| Exact date | 31 August 2027 | Same day in 2025 and 2026; Google's billing table uses 31 August 2027 | Medium |
| Existing-app availability threshold | API 36 | In 2026 it sat one level below the new-app floor | Medium |
| Extension window | Around 1 November 2027 | 2026 precedent; Google's billing table uses 1 November 2027 | Medium to low |
| Wear OS and Automotive floor | Possibly API 36 | Both moved up one level in 2026 | Low |
| Android TV and XR floor | Unknown | TV stayed at API 34 in 2026 | Low |
The billing table is a separate policy, so it supports the pattern without settling it. If your target-37 build is live by June, the exact day in August stops being a risk.
Form-factor floors: Wear OS, TV, Automotive, XR and Android Auto
These levels have applied since 31 August 2026.
| Form factor | New apps and updates must target | Existing apps must target to stay available to new users on newer devices |
|---|---|---|
| Phones, tablets and foldables (Android Auto included) | API 36 | API 35 |
| Wear OS | API 35 | API 34 |
| Android Automotive OS | API 35 | API 32 (Android 12L) |
| Android TV | API 34 | API 33 |
| Android XR | API 34 | API 34 |
- Android Auto follows the phone rule. Google groups mobile and Android Auto in its availability rule, and Android Auto runs through services in your phone app. When the phone app targets 37, so does its car experience.
- Watch and TV builds ship on their own tracks. Play Console has dedicated tracks for Wear OS and Android TV, plus an optional one for XR, so a watch or TV build can sit at a lower target than the phone build. Check that a shared Gradle convention plugin does not raise an untested Wear or TV module to
targetSdk37.
- Android Automotive OS can ride the mobile track. Since December 2024 Play has allowed Automotive OS apps on the mobile release track, so check which track your car build uses. Its 2026 existing-app threshold, API 32, was the lowest of any surface. Raise it when you can test on an Automotive emulator or unit.
- Do not assume 37 everywhere. Until Google publishes the 2027 table, only the phone and tablet floor is safe to plan on.
The Android 17 changes that fire at targetSdk 37
Google's targeted-changes page lists 17 items as of 31 October 2026. We add the per-app Keystore limit from the all-apps page, also gated on targeting 37.
| Change at targetSdk 37 | What breaks | Look first if you |
|---|---|---|
| Widget RemoteViews bitmap memory limit | Oversized updates throw IllegalArgumentException instead of logging a warning | Ship home-screen widgets |
| Lock-free MessageQueue | Code that reflects on its private fields and methods | Use APM, frame-timing or older crash SDKs |
| Static final fields unmodifiable | Reflection throws IllegalAccessException; JNI writes crash | Patch constants in tests or native code |
| Accessibility text-change types | Standard TextView reports them by default | Maintain a custom InputConnection |
| Encrypted Client Hello | Used where your networking library and the server support it | Sit behind SNI-filtering middleboxes |
| ACCESS_LOCAL_NETWORK enforced | LAN discovery and connections without the permission or a system picker | Cast, control smart devices or print locally |
| Passwords hidden on physical keyboards | All password characters hidden by default | Build kiosk or tablet apps |
| SMS OTP protection for standard SMS | OTP messages withheld from your app for three hours | Read SMS for OTP auto-fill |
| Background activity launch hardening | Legacy MODE_BACKGROUND_ACTIVITY_START_ALLOWED usage | Start activities from PendingIntent or IntentSender |
| Certificate Transparency on by default | Connections to servers whose certificates are not CT-logged | Use a private CA |
| Safer native dynamic code loading | System.load() of writable files throws UnsatisfiedLinkError | Download native libraries at runtime |
| Contacts: PII columns removed from the data view | ACCOUNT_NAME, ACCOUNT_TYPE and ACCOUNT_TYPE_AND_DATA_SET disappear from ContactsContract.Data | Sync or deduplicate contacts |
| Contacts: strict SQL without READ_CONTACTS | Incompatible query patterns throw | Build selection strings by hand |
| setContentCaptureEnabled(false) ignored | Content Capture stays on; use FLAG_SECURE instead | Hide sensitive screens from on-device AI |
| Background audio hardening | Background audio needs a while-in-use foreground service, or exact-alarm permission with alarm streams | Build alarm, media or meditation apps |
| Large-screen resizing opt-out removed | Orientation and aspect-ratio locks ignored at sw600dp and above, games excepted | Ship portrait-locked phone layouts |
| Bluetooth RFCOMM read() | Returns -1 on close instead of only throwing | Talk to Bluetooth Classic devices |
| Per-app Android Keystore limit (all-apps page) | Key creation fails above 50,000 keys | Create keys per session or per item |
Two items are new since our August guide. Archived copies show 15 targeted items in mid-August 2026 and 17 by 1 October, the additions being the widget limit and the Content Capture change. Diff the page again before you freeze your plan.
The SMS OTP row will hurt Indian consumer apps most. SMS Retriever needs an 11-character app hash in every OTP message, so the template changes; SMS User Consent works with your current format but asks the user to allow access to one message. Our Android 17 SMS OTP guide covers the migration.
On large screens (smaller dimension of 600dp or more), an app targeting 37 can no longer restrict orientation, resizability or aspect ratio through screenOrientation, setRequestedOrientation(), resizeableActivity, minAspectRatio or maxAspectRatio. Games flagged through android:appCategory are exempt, and Google suggests testing on Pixel Tablet and Pixel Fold emulators. Our adaptive layout guide for targetSdk 37 covers the fixes.
Minor SDK releases: why 37.1 and 37.2 do not move your target
Google's 13 February 2026 post said the Q2 release is the only one with planned app-breaking behaviour changes, with a minor SDK adding APIs in Q4. Google's Android 17 site now carries API diffs for 37.1 (QPR1, API-stable since its Beta 6) and 37.2 (QPR2, in beta).
Three points follow:
- The Play floor has so far named a whole API level: 35, then 36, then 37 for 2027. The August 2027 work is the API 37 list above.
- The targeted changes apply only to apps whose
targetSdkVersionis 37 or higher, so compiling against 37.1 or 37.2 does not switch them on.
- Look one year ahead now. Google's all-apps page says Android 18 will stop granting URI permissions automatically for
ACTION_SEND,ACTION_SEND_MULTIPLEandACTION_IMAGE_CAPTUREintents, and thatusesCleartextTrafficwill be deprecated in a future release. On 21 October 2026 Google also said apps targeting the next Android release will lose direct contact writes throughWRITE_CONTACTS. Fix them while you are in the code.
Extension requests: how they worked in 2026
Google's 2026 process is the best guide to 2027, not a promise.
- Who gets a form. Only apps that are out of compliance see a policy warning and notification in Play Console.
- Where it is. The form sits on the details page of the warning on the Policy status page, and affected apps also get a link in Notifications.
- What it bought. Distribution to all Google Play users until 1 November 2026, for apps that planned to update to the required level.
- What the policy says happens next. Apps still below the availability threshold stop being discoverable to new users on newer Android versions; existing installs are untouched.
Keep an extension for a real blocker, such as an SDK with no compatible release. In 2026 the window ran 62 days (about nine weeks). Nothing guarantees the same in 2027.
A dated checklist working back from August 2027
This is our recommended plan, not Google's. It assumes a 31 August 2027 deadline, 297 days (about 42 weeks) after 7 November 2026, and one phone module.
| Window | Work | Done when |
|---|---|---|
| Nov to Dec 2026 | Inventory every app, form factor, track and targetSdk; list SDKs; start any SMS OTP template change with your gateway | One sheet shows every app and its gap to 37 |
| Jan to Feb 2027 | Compile against API 37; switch targeted changes on one at a time with the compatibility toggles; open tickets with SDK vendors | Every targeted change has an owner |
| Mar to Apr 2027 | Set targetSdk to 37 on a branch; fix large-screen layouts, local network access, TLS with CT and ECH, widgets, Content Capture and audio | The branch passes on Android 17 phones, a tablet and a foldable |
| May 2027 | Internal and closed testing on Android 17 devices; decide Wear OS and TV targets separately | Test tracks are clean for two weeks |
| Jun 2027 | Staged production rollout of the target-37 build | 100% rollout with stable Android vitals |
| Jul 2027 | Buffer; check the Play Help page for the formal rule and the form-factor floors; file an extension only for a named blocker | Nothing open on the Policy status page |
| Aug 2027 | Requirement in force (31 August if the pattern holds) | All later updates target 37 |
The compatibility toggles work on debuggable builds and test one targeted change at a time without raising targetSdkVersion. If you are on API 35 or lower, ship API 36 as its own release first; our API 36 Play deadline checklist covers it. Two sets of behaviour changes in one rollout make regressions hard to trace.
Notes for Indian teams and agencies
- OTP flows set the critical path. Inbox-reading OTP auto-fill stops working at targetSdk 37, because the message reaches your app three hours late. If you move to SMS Retriever, ask your SMS gateway whether adding the hash means updating your registered DLT template, and start that in December, not June.
- Agencies should batch by gap, not by client. Sort client apps by distance from API 37 and form factor, and schedule large-screen and SMS work first: both need design or third-party time.
- Billing lands on the same day. Google's Play Billing Library table says new apps and updates must move off version 8 by 31 August 2027, with extensions to 1 November 2027. Plan both upgrades as one release train. Our guide to the Play Billing Library 8 deprecation covers the billing side.
How eCorpIT can help
eCorpIT is a Gurugram-based technology organisation, founded in 2021, assessed at CMMI Level 5 and MSME certified, with senior-led engineering teams working across AWS, Microsoft and Google platforms. Our mobile application development team runs target-API upgrades as planned work: a portfolio inventory by form factor, an SDK audit, the SMS OTP move, large-screen fixes and a staged rollout watched on Android vitals. Talk to us at /contact-us/.
Last updated: 7 November 2026.
