Google released Android 17 (API level 37) on June 16, 2026 Android 17 official launch announcement. The release formalizes two mandatory platform shifts for developers: all new apps and app updates targeting API level 37 must support large-screen resizability, and native on-device AI agent integration is now a first-class platform feature via the new AppFunctions API same source.
The resizability mandate applies to all apps targeting API level 37, with no opt-out pathway for orientation locks or fixed aspect ratio constraints on devices with screen widths exceeding 600dp. Only apps categorized as games on the Google Play Store are exempt from the requirement Android 17 launch announcement.
The Android system will now ignore all legacy manifest attributes and runtime APIs designed to lock app orientation or enforce fixed aspect ratios, including screenOrientation, setRequestedOrientation(), resizeableActivity=false, and minAspectRatio/maxAspectRatio constraints. Developers building for API level 37 must now build apps to natively support free-form windowing, respect user-preferred device postures, and adapt to any window size without triggering a full UI redraw same source.
Google is explicitly repositioning Android from a traditional mobile operating system to an “intelligence system” with this release, prioritizing deep integration between on-device hardware, system software, and local AI models to deliver context-aware experiences that anticipate user needs Android 17 launch announcement.
The core of this shift is the expanded AppFunctions API, paired with a corresponding Jetpack library currently in alpha. This library lets developers expose their app’s distinct executable features as callable tools for Android MCP, the on-device counterpart to the open Model Context Protocol same source.
The architecture lets AI agents and assistants including Google Gemini automatically discover and execute AppFunctions to complete multi-step workflows on a user’s behalf, with direct access to the app’s local state rather than relying on external API calls or cloud processing same source.
Implementation requires minimal developer work: the Jetpack library supports adding functions via simple class annotations and KDoc comments that describe the function’s purpose for LLM tool-calling. For example, Google’s published sample code demonstrates a note-taking app’s createNote function implemented with the @AppFunction annotation in less than 10 lines of Kotlin, requiring no custom agent logic from the developer Android 17 launch announcement.
To reduce friction further, Google launched an AppFunctions agent skill that automatically analyzes an app’s key workflows, generates required Kotlin code, optimizes KDoc for LLM compatibility, and provides ADB commands for testing and debugging same source. Gemini integration with AppFunctions is currently in private preview for a limited group of trusted testers same source.
Google reports that more than 580 million large-screen devices are already in active user hands Android 17 launch announcement.
Alongside the resizability mandate, Android 17 introduces three new large-screen multitasking features.
App Bubbles let users long-press any app icon on the launcher to turn it into a floating, resizable bubble for lightweight multitasking across phones, foldables, and tablets; the Bubble Bar is a dedicated taskbar section on large screens to organize, switch between, and dock floating app bubbles; and interactive Picture-in-Picture (PiP) for desktop environments allows pinned PiP windows to remain fully interactive rather than read-only, staying always on top of other open applications same source.
Android 17 also updates default activity recreation behavior to eliminate unnecessary restarts and stutter during common configuration changes that do not require a full UI redraw Android 17 launch announcement.
The system will no longer restart running activities by default for changes to keyboard configuration (CONFIG_KEYBOARD, CONFIG_KEYBOARD_HIDDEN), navigation bar visibility (CONFIG_NAVIGATION), touchscreen availability (CONFIG_TOUCHSCREEN), or display color mode (CONFIG_COLOR_MODE) same source. Instead, activities will receive these updates via the onConfigurationChanged() callback, enabling smooth transitions without full UI reloads same source.
Apps that explicitly rely on a full activity restart to reload resources for these configuration changes must now opt in to the old behavior using the new android:recreateOnConfigChange manifest attribute, a breaking change for unupdated apps targeting API level 37 same source.
Bottom line: Android developers targeting API level 37 must update their apps to support free-form windowing and eliminate orientation locks for large-screen devices before submitting any new updates to Google Play, while teams building AI-powered workflows can integrate the AppFunctions API to add on-device agent support to their apps.
