Why Now Daily.

Published

Android 17 Adaptive Apps: What Changes on Foldables and Tablets

Android 17 removes the Android 16 opt-out that let targeted apps retain fixed orientation, aspect-ratio or resizing rules on large displays, so many apps must handle changing window sizes on tablets, foldables and desktop-style windows.

Timeline

  1. 2025: Android 16 established large-screen orientation and resizing overrides but offered a temporary developer opt-out.
  2. 2026-03-26: Android 17 Beta 3 reached Platform Stability, locking the API surface for final compatibility testing.
  3. Android 17 onward: Apps targeting API level 37 can no longer use the Android 16 opt-out on qualifying large screens.

Android 17 changes the default contract for apps on many large displays. For an app that targets Android 17, or API level 37, orientation, resizability and aspect-ratio restrictions no longer apply when the display’s smallest width is greater than 600 density-independent pixels. The app fills the available display window instead of relying on a fixed portrait or landscape presentation or on pillarboxing. This is a platform behavior for qualifying apps and screens, not a promise that every app automatically gains a polished tablet layout. [1][2]

The change completes a transition begun in Android 16. Android 16 could override these restrictions on large screens, but developers targeting that release had a temporary way to opt out. Android 17 removes that opt-out for apps targeting API level 37. Google’s release notes say Beta 3 reached Platform Stability on March 26, 2026, meaning the API surface was locked and developers could conduct final compatibility work against the stable behavior. [1][2]

Several familiar controls are ignored in the affected configuration. The official list includes the manifest attributes screenOrientation, resizeableActivity, minAspectRatio and maxAspectRatio, plus runtime orientation requests such as setRequestedOrientation(). As a result, a layout designed only for a narrow portrait phone can be stretched, expose empty space, place controls off screen or mishandle a camera preview when the user rotates, unfolds or resizes the window. [1][3]

The scope has important limits. Google exempts games identified through the appCategory flag, screens whose smallest width is below 600dp, and cases where a user explicitly chooses the app’s default behavior in device aspect-ratio settings. The rule also depends on the app targeting Android 17. Consumers therefore should not expect identical behavior from every app immediately, and a phone’s outer display may behave differently from a large unfolded inner display. [1][2]

For developers, the practical task is to make layout decisions from the space actually allocated to the app rather than from a hardware label such as “tablet.” A foldable can move between a phone-sized window and a tablet-sized one, while a tablet app can occupy only part of the screen in split-screen or desktop windowing. Android’s guidance recommends current window metrics and window size classes so navigation, content density and pane structure respond to the available window. [3]

Fold-aware design adds another layer. Android’s Compose guidance exposes folding features such as hinge orientation, whether the device is flat or half opened, and whether a hinge separates the usable area. An app can keep important controls away from a hinge, use the fold as a natural divider, or switch between one- and two-pane arrangements. Those techniques are design options; Android 17’s mandatory resizing behavior does not itself invent a two-pane interface. [4]

The durable takeaway is that Android 17 raises the cost of assuming one orientation or aspect ratio. Developers should test rotation, folding and unfolding, split-screen, desktop-style resizing, state restoration and camera previews on affected large screens. Users may see more apps fill their windows, but visual quality still depends on each app’s implementation. Google’s compatibility rules establish the minimum platform behavior, while responsive and adaptive layouts determine whether the result is merely functional or genuinely useful. [1][3][4]

Sources

  1. Android Developers — Restrictions on orientation and resizability are ignored
  2. Android Developers — Android 17 release notes
  3. Android Developers — Support different display sizes
  4. Android Developers — Make your app fold aware

Related stories