What changes, and when
There are two separate April 2027 requirements. One concerns how the app behaves. The other concerns what the store listing contains.
- Tier 3 baseline for foldables. Apps that don't meet it "will no longer be able to publish or update on Google Play", according to Google's announcement, and may also lose visibility in the store. Google says existing apps that aren't updated remain downloadable. Google does not say they will be pulled from users' devices.
- Foldable screenshots. From April 2027, new apps and listing updates must include three foldable screenshots on top of the usual two phone screenshots. This is a Play Console submission requirement for new apps and store-listing updates. Google says developers can already upload foldable screenshots, and they begin appearing in listings over the coming weeks.
- Scope. This is a Google Play distribution rule. Nothing in the announcement makes it a universal Android requirement for apps distributed elsewhere.
What Tier 3 actually demands
Tier 3 is the lowest of Google's three tiers, called "Adaptive ready". It is a baseline, not an optimisation target.
- Fill the screen. Apps must fill the available display area without letterboxing or compatibility modes.
- Keep state. Apps must preserve state during rotation, folding, unfolding and resizing. Google's examples are scroll position, text input and media playback.
- Support multi-window. Apps must work in multi-window environments.
- Layout can be imperfect. Google's quality guidelines say the layout at this tier might not be ideal, but users must still be able to complete critical task flows.
Higher tiers are optional for now:
- Tier 2 covers responsive multi-pane layouts, avoiding stretched UI, and basic support for keyboard, mouse, trackpad and stylus input.
- Tier 1 covers differentiated experiences such as tabletop and book postures, camera continuity, interactive picture-in-picture and multi-instance support.
Apps that meet Tier 2 and Tier 1 support can apply for badging and enhanced merchandising on Google Play. Google also says the framework will progressively expand to incorporate Tier 2 and Tier 1 standards across foldables, tablets, Googlebooks, and Android XR. Today's minimum is only the first step.
Games and the API 37 deadline
Games run on a different clock. Titles will need foldable screenshots in listings by April 2027, while Tier 3 large-screen quality guidelines go into effect in August 2027. The UC Today brief compressed this into "similar rules for games from August 2027". More precisely, the screenshot rule starts in April and the quality rule starts in August. Google says game criteria are tailored to engines, viewports and touch controls.
August 2027 also brings a separate milestone for apps. Google says new and updated apps must target API level 37 (Android 17), which removes developer opt-outs for orientation and resizability restrictions on large screens. That is a different requirement from the April Tier 3 and screenshot rules, so keep them apart in planning.
Screenshot specifics
Google's screenshot guidance gives concrete formats:
- A foldable set is three to eight images covering 1:1 and 4:3 inner-display ratios, plus at least one portrait image for the 10:16 folded outer screen.
- For foldables with a 1:1 inner display, include at least one unfolded 1:1 screenshot.
- For foldables with a 4:3 inner display, provide at least one unfolded 4:3 screenshot and at least one folded 10:16 portrait screenshot. A 16:10 landscape is optional.
- Google's Android CLI guide lists example emulator output sizes of 2106 × 2106 px (1:1), 2688 × 2016 px (4:3) and 1260 × 2016 px (10:16). Those are examples from the guide, not the only acceptable sizes.
- Screenshots can come from physical devices or the Android Emulator. Google says captures from the 1:1 and 4:3 foldable emulators are fully compliant with the new requirement.
- Check that each image shows a fully loaded UI without system dialogs, and that it meets Play Console's dimension and 8 MB file-size limits.
- Upload the images in Play Console under Grow > Store presence > Store listings.
One trap from the CLI guide: the 9:16 folded outer screen of the 1:1 foldable profile belongs in the Phone section, not the Foldable section. Uploading it to the Foldable section triggers an invalid-dimension error.
A practical preparation checklist
- Test on the right device types. Google's guidelines list a foldable with a 1:1 inner display (802×802 dp) and one with a 4:3 inner display (1024×768 dp) among the minimum test targets.
- Run the four Tier 3 behaviours. Fold, unfold, rotate and resize the app mid-task, then confirm that scroll position, typed text and playback survive.
- Look for letterboxing. Any black-bar or compatibility-mode behaviour on an unfolded inner display will fail the baseline.
- Try split-screen. Run the app beside another app.
- Capture screenshots separately. Treat the listing assets and the runtime behaviour as two tasks.
- Check your toolkit. Google points to Jetpack Compose for adaptive layouts, and to the Compose adaptive skill in Android Studio or the Android CLI.
Analysis
The screenshots are easy to produce and easy to verify. Tier 3 is the real work, because it tests whether the app adapts at runtime. A polished screenshot set doesn't show that the app passes the quality bar. Apps locked to portrait or built around fixed-size layouts are the likeliest to struggle. Teams with older View-based codebases may have the most refactoring to do. That last point is general industry reasoning, not something Google's announcement states.
Google's wording suggests a deliberately modest threshold, since the Tier 3 checklist tolerates less-than-ideal layouts. The stronger incentives are the optional ones: badging and merchandising for Tier 1 and 2 apps. As other outlets have noted, the framework is expected to widen beyond foldables to tablets, Googlebooks and Android XR. That makes foldable compliance a sensible foundation for broader large-screen work rather than a one-off chore.
For users, the aim is fewer apps that look stretched or boxed on a foldable's inner display. For developers, the message is to start testing now, since April 2027 arrives quickly.
References
- Google will require Android apps to support foldables from April 2027 - UC Today UC Today · 2026-11-19T10:04:59.890000+00:00
- Elevating apps: New adaptive quality standards on Google Play | Android Developers' Blog developer.android.com
- Google Play wants Android apps to nail foldable basics by April 2027 9to5google.com