Android 17 Features: What's New and What Breaks for Your App

Android 17, released as API level 37 in June 2026, introduces new capabilities including Handoff, privacy-preserving contact selection, encrypted TLS client hello, profiling triggers, hybrid post-quantum APK signing, AppFunctions for on-device agents, and expanded bubble support, while shifting new Android development guidance toward Jetpack Compose. It also changes behavior for all apps regardless of target SDK, notably by imposing RAM-based memory limits, delaying certain SMS OTP access, restricting background audio actions, altering keyboard restoration and activity configuration behavior, and changing Bluetooth and cross-profile networking behavior. Apps targeting API 37 face additional compatibility requirements, including mandatory resizability on large screens and foldables except for games, local-network permission requirements, default Certificate Transparency enforcement, restrictions on reflective MessageQueue access and mutable static fields, read-only native-library loading, revised background-launch rules, widget bitmap limits, and updated Bluetooth, content-capture, NPU, notification, and SMS handling. The recommended migration approach is to first test an unchanged production build on Android 17, then use compatibility toggles in debuggable builds to isolate API 37 changes before raising the target SDK, with particular attention to foldable layouts, memory-related process kills, permissions, server certificates, and runtime reflection. Android 17 can be tested on supported Pixel phones and Galaxy Z Fold8 devices through TestMu AI’s real-device platform, while Android 17 QPR1 does not introduce app-impacting API changes; developers are also advised to prepare for Android 18 changes affecting URI permissions and cleartext traffic.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.