Published November 22, 2026
Google Play Sets an April 2027 Deadline: Foldable Apps Must Clear Adaptive Tier 3
Google Play announced on November 18 that it will attach a quality gate to foldable support. Starting in April 2027, apps will have to meet Tier 3 of the Android adaptive app quality guidelines for foldables before they can publish. Tier 3 is described as Adaptive ready, or basic support, which is the detail worth holding onto: this is not a push toward excellent large screen design, it is a deadline for the floor.
For a Flutter codebase the practical question is narrower than it first appears. Most Flutter apps already avoid the specific failure the new rule targets, and most of them still have at least one screen that would fail it. The difference between those two statements is where the work lives.
What Tier 3 actually requires
The requirements are concrete and short. An app must not use letterboxing or any other compatibility mode, and must fill the entire screen on a foldable. Through rotation, window resizing, and folding or unfolding, it must preserve scroll position, text input, and media playback. It must also function in multi-window environments.
Those four behaviors are one behavior seen from four angles: the app has to treat a window size change as normal, not as a relaunch. Everything Tier 3 asks for follows from that.
The consequence for non-compliance is stated plainly. Apps that do not meet the bar will not be able to publish or update on Google Play, and may see reduced visibility on the store. Foldable screenshots also become a standard submission requirement for new apps and for any update that touches a store listing.
Two more dates sit around that deadline. By August 2027, new and updated apps must target Android 17, API level 37. And the framework is explicitly described as expanding over time to Tier 2 and Tier 1 across foldables, tablets, Googlebooks, and Android XR, so April 2027 is the first gate rather than the only one.
The tier ladder above the floor
Tier 3 is the pass mark. The two tiers above it are optional and rewarded with store badging, editorial spotlighting, and enhanced merchandising:
- Tier 2, Adaptive optimized, evaluates responsive multi-pane layouts, penalizes stretched UI elements, and expects basic support for external keyboards, mice, trackpads, and styluses.
- Tier 1, Adaptive differentiated, evaluates tabletop and book postures, camera continuity, interactive picture-in-picture, and multi-instance support for media, video, reading, and multitasking apps.
Games follow a separate but parallel track. Foldable screenshots are required in game listings by April 2027, while the Tier 3 large screen quality guidelines for games take effect in August 2027. A game at Tier 3 must render full screen in its supported orientations with unobstructed HUD safe areas, letterbox or pillarbox inside the engine when rotated to an unsupported orientation, and hold state and touch alignment across folding, unfolding, rotation, and multi-window resizing.
At Tier 2, games add high-resolution graphics, proportional HUD scaling, styled visual framing when letterboxing, smooth frame pacing, and full playability with external controllers, keyboards, and mice. Tier 1 asks for sustained 60 frames per second, 120 on supported displays, thermal and battery stability across long unfolded sessions, and dynamic resolution scaling between the inner and cover screens.
Where a Flutter app is likely to fail
Flutter renders its own widgets rather than relying on the platform view system, so letterboxing is rarely the problem. The common failures are subtler and usually come from assumptions embedded in a layout rather than from a missing feature.
A fixed orientation declared in the manifest is the clearest case. So is a screen built on OrientationBuilder alone, which treats a foldable as phone or tablet and ignores the continuous resize that folding produces. Hard-coded pixel widths, images with BoxFit.cover inside a fixed aspect ratio, and grids with a fixed column count all stretch or crop when the inner display is wider than the window the widget was designed for.
State preservation is the part that catches people. A widget rebuild after a resize is normal, but losing scroll offset, half-typed text, or a playing video is not. PageStorageKey and AutomaticKeepAliveClientMixin cover list position and widget lifetime. Text survives if the controller lives above the rebuilt subtree rather than inside it. Video needs a controller owned by a state object that is not recreated when constraints change.
Multi-window is the requirement most often assumed rather than tested. Flutter handles multiple windows on desktop through the windowing APIs that shipped in August, and on Android it receives the resized window like any other. Neither works if the app quits to a splash screen whenever it loses focus.
A practical order of work
Audit the manifest for locked orientations first, because that is a one-line fix with an outsized effect on how the rest of the app behaves. Then exercise every primary screen on a foldable emulator while dragging the window size instead of rotating the device, since dragging exposes resize handling that rotation hides. Finally, test the three state categories the guidelines name by name: scroll position, text input, and media playback.
None of that requires a redesign. It requires proving that the app survives being resized, which is a different test from the one most teams run today. With April 2027 on the calendar and a publishing block attached to failure, it is also a test worth adding to CI before the deadline adds it for you.