Android 17 Is Released: What Its Behavior Changes Mean for Existing Apps
Google released Android 17 on June 16, 2026. In its announcement on the Android Developers Blog, the company said the new version (API level 37) is available on most supported Pixel devices, that the source code has been published to the Android Open Source Project, and that beta builds are available on devices from partners including Honor, Lenovo, OnePlus, OPPO, vivo and Xiaomi.
For a business that already has an app in the store, the new features matter less than a quieter list: the behavior changes. Some apply to every app as soon as a customer's phone updates, whether or not you have shipped a new build. Others apply only once your team raises the app's target SDK version to 37. If you own or are planning Android app development work, that split decides what needs testing now and what can be scheduled.
This article covers what is released, which changes are most likely to affect an existing app, and how to plan the work.
What Google released on June 16, 2026
Three things have different statuses and are worth keeping apart. Released and available now: Android 17 itself, on most supported Pixel devices, along with the final API level 37 SDK. In beta at the time of the announcement: Android 17 on the partner devices Google listed. The post does not give dates for those manufacturers, so the pace at which your non-Pixel users move to Android 17 will depend on each device maker.
Preview only: the announcement describes AppFunctions, a way for an app to expose its features as tools that AI assistants can call. Google states that the supporting Jetpack library is in alpha and that the Gemini integration is in private preview with an early access program. It is not something to plan a production launch around yet. Google also wrote that it plans a "fast-paced release cadence" from here on, without publishing a schedule.
Changes that affect every app on an Android 17 device
Google documents these on its behavior changes for all apps page. They take effect on the user's device regardless of how your app was built, so an app you last updated a year ago is still in scope.
App memory limits
According to that page, Android 17 introduces memory limits based on the device's total RAM, aimed at memory leaks and extreme outliers. The announcement post is blunter: processes that exceed the limit are terminated. To the user this looks like the app closing without warning. Google's documentation says an affected app can identify these exits afterwards because the system records an exit description containing "MemoryLimiter:AnonSwap". Google does not publish the limit as a single figure, so neither do we.
One-time passcodes sent by SMS
The same page explains that messages in the WebOTP format are now withheld for three hours from apps that have SMS read permission but are not the intended recipient. Google recommends moving to its SMS Retriever or SMS User Consent APIs. If your app reads incoming text messages to auto-fill a login or payment code, this is the change to test first.
Background audio, keyboards and work profiles
Google also lists restrictions on audio playback, audio focus requests and volume changes made while an app is in the background, and notes that these calls can fail silently rather than raise an error. Two smaller items: the on-screen keyboard is no longer automatically restored after a rotation in some cases, and network traffic between a personal profile and a work profile on the same device over the loopback address is blocked by default.
Changes that apply once your app targets API level 37
The second group is on Google's behavior changes for apps targeting Android 17 page. Nothing here changes until your developers raise the target SDK version, which gives you control over timing.
Large screens can no longer be opted out of
On tablets, unfolded foldables and other displays with a smallest width of around 600dp or more, Android 17 ignores an app's orientation, resizability and aspect ratio restrictions. Google's documentation says developers could opt out of this at API level 36, and that the opt-out is no longer available for apps that target Android 17. The announcement adds that games, identified by their Google Play category, remain exempt. In practice, an app that was designed as portrait-only for phones will be shown in landscape and in resizable windows on those devices, and its layouts need to cope.
Local network access needs a permission
Apps that talk to devices on the local network, such as printers, card readers, smart TVs, or factory and warehouse equipment, must request a new runtime permission named ACCESS_LOCAL_NETWORK or use the system's device pickers. Without it, those connections are blocked for apps targeting API level 37.
Stricter security defaults
The same page lists several security defaults that change at this target level: certificate transparency is enabled by default for secure connections, Encrypted Client Hello is enabled for TLS, native libraries loaded by the app must be read-only, and fields declared static final can no longer be modified through reflection. Standard SMS messages containing one-time passcodes also become subject to the three-hour delay. Most business apps will not notice these directly, but older third-party SDKs sometimes rely on the patterns being closed off, which is why a dependency review is part of the upgrade.
Compose-first: the View system moves to maintenance mode
The announcement includes a statement with longer-term consequences. Google says all new Android APIs, libraries, tools and guidance will be built exclusively for Jetpack Compose, and that the older View-based components, including Fragments, RecyclerView and ViewPager, are now in maintenance mode and will receive only critical bug fixes.
That is not a removal. Apps built with XML layouts continue to run and can still be updated. It does mean new platform capabilities will arrive in Compose first, or only in Compose.
Changes Google has announced for later releases
Two items on the all-apps page are notices rather than current behavior. Google says the usesCleartextTraffic manifest setting will be deprecated in a future release and that apps needing unencrypted HTTP connections should move to a network security configuration file. It also says that, starting in Android 18, the system will stop automatically granting file access permissions when an app shares content or launches the camera through certain standard intents; apps will have to grant that access explicitly. Neither affects users today.
What this means for your business
The following is our reading of the announcement, offered as guidance. The practical risk sits in the first group of changes, because you do not choose when they arrive. A customer on a Pixel phone may already be running your current build on Android 17. If your app is memory-heavy (large image galleries, maps, video, long sessions) or depends on reading SMS codes or playing audio in the background, it is worth confirming how it behaves there before support tickets tell you.
The second group is a budgeting question. Large-screen support is the item most likely to need design time rather than just engineering time, particularly for apps that were locked to portrait. If your app is built with Flutter or React Native, the same platform rules apply underneath; our comparison of native, Flutter and React Native explains where the framework helps and where the operating system still sets the terms.
What to do next
- Install your current production build on an Android 17 device or emulator and run through sign-in, payments, media and any long-running screens. No code change is needed for this test.
- Ask your developers whether the app reads SMS codes, plays audio in the background, or connects to devices on a local network, and check each against Google's two behavior change pages.
- Open the app on a tablet or foldable, in both orientations and in a resized window, and note what breaks. Scope that work before you raise the target SDK version.
- Ask for a list of third-party SDKs and their Android 17 support status.
- If the app still uses XML layouts, treat a gradual move to Jetpack Compose as a roadmap item, not an emergency.
Conclusion
Android 17 has been available since June 16, 2026, and its effects reach existing apps in two stages: a set of changes that apply on any Android 17 device, led by memory limits and SMS passcode protection, and a larger set that applies when the app targets API level 37, led by mandatory large-screen behavior and the local network permission. Testing the first set costs little and can happen this week.
If you would like a second opinion on how your app is affected, you can request a quote for a compatibility review. Entrant Technologies builds websites, web applications, mobile apps and custom software.