The short version
From April 2027, an Android app that breaks on a foldable can no longer ship updates through Google Play. Google announced the rule on November 18, 2026, and it turns foldable support from a nice-to-have into a release blocker. Teams that build or maintain Android apps for US and EU users should audit layouts and state handling now, while there is still a full planning cycle before the deadline.
What did Google announce?
Google Play is adding adaptive app quality requirements to its publishing rules. Mekka Okereke, general manager of Google Play Apps, set them out on the Android Developers Blog on November 18, 2026. From April 2027, apps must meet at least Tier 3 of Android’s adaptive app quality guidelines for foldables. Apps that fall short “will no longer be able to publish or update on Google Play, and may have reduced visibility on the store,” Google wrote.
The Verge noted the timing: the rule arrived weeks after Apple launched its iPhone Duo foldable, which already counts more than 200,000 optimized apps. Google cites over 580 million large-screen Android devices in use today.
What do the three adaptive quality tiers require?
Tier 3 is the mandatory floor. The two higher tiers are optional for now but earn store badging and editorial placement.
| Tier | What it checks | Status |
|---|---|---|
| Tier 3: Adaptive ready | Fills the display without letterboxing or compatibility modes; keeps scroll position, text input and media playback through rotation, folding, unfolding and resizing; supports multi-window | Required for apps from April 2027 |
| Tier 2: Adaptive optimized | Responsive multi-pane layouts, no stretched UI elements, basic keyboard, mouse, trackpad and stylus input | Optional; eligible for badging now |
| Tier 1: Adaptive differentiated | Tabletop and book postures, camera continuity, interactive picture-in-picture, multi-instance support | Optional; eligible for badging now |
What changes in Play Store listings?
From April 2027, publishing a new app or updating a store listing requires three foldable screenshots on top of the standard two phone screenshots. Developers can upload them today in Play Console under Grow > Store presence > Store listings.
- 1:1 inner display (for example Pixel 11 Pro Fold, Galaxy Z Fold8 Ultra): at least one unfolded screenshot.
- 4:3 inner display (for example Galaxy Z Fold8): at least one 4:3 unfolded screenshot and at least one 10:16 portrait screenshot of the folded outer screen, with an optional 16:10 landscape.
- Phone landscape: a 16:9 landscape screenshot can now sit next to the required 9:16 portrait ones.
Screenshots captured from the foldable profiles of the Android Emulator meet the format rules, so teams without physical devices are not blocked.
What are the key dates?
- November 2026 (live now): foldable screenshots can be uploaded; apps meeting Tier 2 or Tier 1 can apply for badging and enhanced merchandising.
- April 2027: Tier 3 becomes mandatory for standard apps, and foldable screenshots become a submission requirement for apps and games. Existing apps that are not updated stay downloadable.
- August 2027: games must meet the large-screen quality bar, and new apps and updates must target API level 37 (Android 17), which removes developer opt-outs for orientation and resizability restrictions on large screens.
What it means for US & EU software teams
The real risk is not a lower ranking but a blocked release. An app that still letterboxes on a foldable in May 2027 cannot ship its next update, including a security fix or a change a regulator asked for. For banking, insurance and healthcare apps, losing the ability to patch is an operational and compliance problem, not a design one.
The typical Tier 3 failures trace back to familiar patterns: activities locked to portrait, resizeableActivity="false" in the manifest, fixed-width layouts, and screens that lose form input or playback position when the activity is recreated on fold. Apps built with Jetpack Compose and window size classes usually have less to fix than older XML view hierarchies.
Cross-platform apps are not exempt. The rule applies to whatever ships to Google Play, so Flutter and React Native apps need the same fold, unfold and multi-window checks.
Budget the work as a release-train item, not a redesign. Starting the Tier 3 audit, layout fixes and a fold, unfold and rotation test pass in Q1 2027 leaves room for at least one regular release before the April deadline.
How should teams prepare?
- Audit against Tier 3. Run every core flow on 1:1 and 4:3 foldable emulator profiles and note letterboxing, stretched screens and lost state.
- Remove orientation and resize locks. Find
screenOrientationandresizeableActivitysettings now; Android 17 targeting will override them anyway. - Preserve state on configuration changes. Keep scroll position, form input and media playback across fold, unfold, rotation and multi-window resizing.
- Add fold tests to QA. Put foldable profiles into the regression matrix, using Android Device Streaming or emulators if the team has no hardware.
- Prepare store assets. Capture the three foldable screenshots and upload them early, ahead of the next release that touches the listing.
Frequently asked questions
When do the Google Play foldable requirements take effect?
The baseline Tier 3 requirement and the foldable screenshot rule take effect in April 2027 for standard apps. Games must meet their large-screen quality bar by August 2027 but still need foldable screenshots from April 2027. Also in August 2027, new apps and updates must target API level 37 (Android 17).
What does Tier 3 Adaptive ready mean?
The app fills the available display area without letterboxing or compatibility modes, keeps state such as scroll position, text input and media playback through rotation, folding, unfolding and resizing, and works in multi-window mode.
What happens to apps that do not comply?
According to Google, apps that miss the Tier 3 bar will no longer be able to publish or update on Google Play and may have reduced visibility in the store. Existing apps that are not updated remain downloadable.
Which foldable screenshots will Google Play require?
Three foldable screenshots in addition to the standard two phone screenshots: at least one of a 1:1 unfolded inner display, and for 4:3 inner displays at least one 4:3 inner screenshot plus a 10:16 portrait screenshot of the folded outer screen. Screenshots from the Android Emulator foldable profiles are accepted.
Do Flutter and React Native apps have to comply too?
Yes. The rule applies to the app on Google Play, not to the framework it is built with. Cross-platform apps need the same checks for letterboxing, state preservation on fold and unfold, and multi-window behavior.
Sources
Android Developers Blog — Elevating apps: New adaptive quality standards on Google Play (primary source, November 18, 2026)
Android Developers Blog — Elevating games: New large screens and foldables quality standards on Google Play (November 18, 2026)
The Verge — Google is forcing Android app developers to properly support foldables (November 18, 2026)
Android Developers — Tier 3: Adaptive ready guidelines