Skip to content

Guides

Android 17 Behavior Changes for Website Apps: What to Test Before You Target API 37

Most of Google's Android 17 list is native-code-only. A few items do reach an app built from a website. Here is which ones, what applies to every app and what only applies once you target API 37.

12 min read

Android 17 (API level 37) changes a website app in a few specific ways: the large-screen opt-out from Android 16 disappears, the on-screen keyboard is no longer restored after some rotations, and a handful of network, permission and audio rules tighten. Most of Google's Android 17 list is native-code-only and does not touch a site loaded in a web view. This guide sorts the Android 17 behavior changes into what to test, what to ask your app builder and what to ignore.

Which Android 17 behavior changes affect a website app?

Google splits its list in two. One page covers changes that apply only to apps targeting Android 17, and another covers changes that apply to all apps running on Android 17, whatever they target. That split matters: an app that has not moved to API 37 still gets the second list on any Android 17 phone. Google's pages were last updated on November 11 and November 9, 2026, and we checked them on November 20, 2026.

Android 17 changes sorted by likely impact on a website app. The last column is our reading of Google's pages, not a Google statement.
ChangeApplies toWebsite app impact
Orientation, resizability and aspect ratio limits ignored; Android 16 opt-out removedApps targeting API 37, screens 600dp wide or moreTest: your site fills the whole tablet window.
Keyboard visibility not restored after an unhandled configuration change such as rotationAll apps on Android 17Test: type in a form on a tablet, then rotate.
Background audio restrictions; playback and volume calls fail silently outside a valid lifecycleAll apps, stricter at API 37Test only if your site plays audio.
ACCESS_LOCAL_NETWORK runtime permission mandatoryApps targeting API 37Ask your builder, if your site talks to devices on a local network.
Certificate transparency on by defaultApps targeting API 37Ask your builder: Google's page does not say whether web view page loads are covered.
Encrypted Client Hello (ECH) used for TLSApps targeting API 37Nothing for site owners to do on Google's page.
SMS one-time-code protection, three-hour delay for apps that read SMSWebOTP: all apps. Standard SMS: API 37Only affects apps that hold SMS-reading permission.
App memory limits based on device RAMAll apps on Android 17Test long sessions on heavy pages.
Widget memory limits, MessageQueue, static final fields, native library loading, BluetoothMostly API 37Native code only. A site in a web view does not use them.

What changes on tablets once an app targets API 37?

Two Google pages combine into one practical problem. First, for apps targeting API 37, orientation, resizability and aspect ratio restrictions no longer apply on screens at least 600dp wide, and Android 17 removes the temporary opt-out that Android 16 offered. Games, users who opt in through the device's aspect ratio settings, and screens under 600dp are exempt (source: Google's large-screen page). Our Android 16 guide covers the layout side in detail.

Second, Google says that from Android 17, when a configuration change such as rotation is not handled by the app itself, the keyboard's previous visibility is not restored; the app must ask for it explicitly. Google also warns that allowing rotation causes more activity re-creation, which can lose state that is not saved. Put together, a person typing in a form on a tablet may rotate the device and find the keyboard gone, or the form reset. Whether a given wrapper app handles this is not something Google's pages say, so test it on a real tablet.

Do the network changes matter for a website app?

Mostly no, with one exception to watch. Encrypted Client Hello hides the server name during the TLS handshake. For apps targeting API 37 it is used only when the networking library has ECH support and the server supports it, and Google names WebView among the examples of such libraries. If it cannot be negotiated, the client sends a placeholder extension instead. Nothing on Google's page asks website owners to act.

Certificate transparency is different because the page is silent on scope. For apps targeting API 37, Google says it is enabled by default, where Android 16 apps had to opt in. It does not say whether pages loaded in a web view are covered, so ask your app builder and check that your site's certificate comes from a mainstream authority.

Cleartext traffic is an announced plan, not an Android 17 change. Google says it intends to deprecate the usesCleartextTraffic manifest element in a future release, and that apps needing plain http connections should move to a network security configuration file, which is supported from API 24. If an app supports older versions, Google says to do both. A site that still links to http:// addresses already has trouble today; see ERR_CLEARTEXT_NOT_PERMITTED in a website app.

What about the local network, SMS and contacts changes?

For apps targeting API 37, the ACCESS_LOCAL_NETWORK runtime permission is mandatory for talking to devices on a local network, such as smart home devices or casting receivers. Apps can instead use system-mediated device pickers and skip the prompt. Android 16 let apps opt in; Android 17 makes it required. Google does not discuss web content in this section, so a site that reaches local devices is a question for your builder.

The SMS one-time-code delay applies to apps that have permission to read SMS messages, so a website app that does not request that permission is not the target. The Contacts changes in the API 37 list are about the Contacts Provider's data, which is native code. The Google Play policy side, including precise location and READ_CONTACTS declarations, is covered in our guide to the Google Play location button policy.

What should a site with audio or heavy pages check?

Google says audio playback, audio focus and volume-change calls now need to start from a valid app state. Outside one, playback and volume calls fail silently, and audio focus requests return a failure code. For apps targeting API 37, an app that touches audio in the background must run a foreground service with while-in-use capabilities, with a narrow exception for exact-alarm apps playing alarm streams. If your site is a radio or podcast player, lock the screen mid-playback and see what happens.

App memory limits scale with the device's RAM and are aimed at leaks and outliers, according to Google. Google's pages do not single out web views, so the sensible test is a long session on your heaviest page, such as a large catalog or a long feed.

How do I test a website app before it targets API 37?

  1. 1

    Find out what your app targets

    Our target API level guide explains how to check it, and what Google Play currently requires.

  2. 2

    Use a tablet running Android 17

    Rotate while typing in a form, and check that the keyboard and field values survive.

  3. 3

    Resize and split the window

    Check your layout at widths around 600dp and above, since orientation limits no longer apply there.

  4. 4

    Play audio and lock the screen

    Only needed if your site has audio. Note whether playback stops or fails silently.

  5. 5

    Ask your builder three questions

    Does it handle certificate transparency, local network access and keyboard state after rotation on API 37?

  6. 6

    Re-test after every rebuild

    Run the same checks on a real phone and a tablet each time the app is rebuilt.

Frequently asked questions

Which Android 17 changes apply even if my app does not target API 37?
Google's all-apps list applies on any Android 17 device regardless of target. It includes app memory limits, the keyboard-visibility change after unhandled rotation, background audio restrictions, SMS one-time-code protection for WebOTP messages, and blocking of cross-profile loopback traffic.
Can I still opt out of the large-screen orientation change in Android 17?
No. Google says Android 17 removes the temporary opt-out that Android 16 provided, for apps targeting API 37. Games, users who opt in through the device's aspect ratio settings, and screens under 600dp are exempt.
Why does the keyboard disappear when I rotate a tablet in my app?
From Android 17, Google says the keyboard's previous visibility is not restored after a configuration change the app does not handle itself. The app has to request the keyboard explicitly, so ask your app builder how rotation is handled.
Does Encrypted Client Hello change anything for my website?
Google's page does not ask website owners to act. For apps targeting API 37, ECH is used only if the networking library and the server both support it; otherwise the app sends a placeholder extension.
Is certificate transparency checked for pages loaded in a web view?
Google says certificate transparency is on by default for apps targeting API 37, but its page does not say whether web view page loads are covered. Ask your app builder, and use a certificate from a mainstream authority.
Does Google Play require me to target Android 17 now?
This guide covers behavior changes, not the Play deadline. Our target API level guide explains the requirement and how to check what your app targets.