November 21, 2026

Google Play foldable requirements: April 2027 checklist

Google Play requires Tier 3 adaptive quality and 3 foldable screenshots from April 2027, then API 37 in August. What to test, capture and change.

News

Tech

From April 2027, new apps and updates on Google Play must meet Tier 3 adaptive quality on foldables and include foldable screenshots. API 37 follows in August and removes the orientation and resizability opt-outs. Test on the two foldable emulators now, capture the screenshots there, and plan API 37 as a separate job. Bundle it with the Tier 3 fixes only if you're editing the same layouts.

What does Google Play require, and from when?

Google set these dates in two Android Developers Blog posts on 18 November 2026, one for apps and one for games. The API 37 behaviours below come from its February 2026 resizability post.

WhenWhat applies
Now (Nov 2026)Foldable screenshot upload; Tier 1 and 2 badging
April 2027Tier 3 on foldables; 3 foldable screenshots at submission
August 2027New and updated apps target API 37; games meet Tier 3

The April gate is a ship gate, not a badge. In Google's words, apps that miss the bar "will no longer be able to publish or update on Google Play, and may have reduced visibility on the store." Apps you never update stay downloadable.

Google hasn't published how Tier 3 is verified or what reduced visibility means in numbers. Watch Play Console messages and the Play Console Help page, and treat the first update after April as the real test. Tier 2 and Tier 1 are optional for now and unlock badging.

Will my app pass Tier 3 on a foldable?

Tier 3 asks for three things: the app fills the display without letterboxing or compatibility mode, it keeps state (scroll position, text input, media playback) through rotation, fold, unfold and resize, and it works in multi-window.

Test on a large-screen device (600 dp class), on Android 12 (API 31) or higher. Use both "Foldable (1:1 inner display)" and "Foldable (4:3 inner display)" emulators.

Each area has test IDs in the guidelines. Run them by group.

Orientation, state and combinations

T-Config_Orientation, T-Config_State and T-Config_Combinations. This is where phone-first apps fail first: a portrait-locked activity letterboxed in the middle of an unfolded screen, or a form that empties when you fold.

Multi-window

T-Multi-Window_Functionality, T-Multi-Window_Focus and T-Multi-Window_Resources. Put your app next to another one and check it still works. Start a video, put another app on top, and check yours keeps playing. If you use the camera or mic, check your app regains it on refocus.

Camera preview and media projection

T-Camera_Preview and T-Media_Projection. Only if your app uses them.

Keyboard, mouse and stylus

T-Keyboard_Input, T-Mouse_Trackpad_Basic, T-Stylus_Basic and T-Stylus_Text_Input. Cheap to pass if standard Compose or View widgets carry your input; expensive if you built custom text fields.

A worked example

Take a phone-first note-taking app (illustrative) that targets API 36 and declares android:screenOrientation="portrait". On foldable_4_3, unfold it and look for letterboxing (T-Config_Orientation). Type a few lines, scroll, then fold and unfold; the text and scroll position must survive (T-Config_State). Then capture the three screenshots in the next section. Fixing the app is usually a layout and state job, not a rewrite. The screenOrientation attribute matters again in August, covered below.

How do I capture the 3 foldable screenshots?

Foldable screenshots live in Play Console under Grow > Store presence > Store listings. You can upload three to eight. If one of the three ratios (1:1, 4:3, 10:16) is missing, the console rejects the upload with "Upload at least 1 screenshot in each of the 1:1, 4:3, and 10:16 aspect ratios". Google says emulator shots from the two foldable profiles are fully compliant, so you don't need hardware.

Console sectionEmulator, postureSize (px)
Foldable 1:1foldable_1_1, unfolded2106 x 2106
Foldable 4:3foldable_4_3, unfolded2688 x 2016
Foldable 10:16foldable_4_3, folded1260 x 2016
Phonefoldable_1_1, folded1053 x 1872

The apps post says a 1:1 device needs only a 1:1 shot, but the console error asks for all three ratios, so capture one of each. The trap is the folded 9:16 shot from foldable_1_1: it belongs in Phone, not Foldable.

The commands below are from Google's screenshot page, which needs emulator 37.3.10 or above. They use the android command, covered in our piece on Android CLI commands and skills.

Bash
android sdk update emulator
android update
android emulator create foldable_1_1
android emulator create foldable_4_3
android emulator start foldable_4_3
adb emu unfold
adb emu fold
# capture each posture with adb shell screencap -d <display-id>; get the IDs from
# adb shell dumpsys SurfaceFlinger --display-id (line 1 inner, line 2 outer)
file play_screenshots/*/*.png

Check the output of file for dimensions, and keep each image under 8 MB. The captures are raw images, not finished marketing assets, so you'll want to frame them yourself.

Search more than 300,000 open roles in one place
From more than 19,000 companies across the UK, the US and Spain. Free during the open beta, until the end of November.
Try Job Search

What changes when I target API 37 in August 2027?

Google's apps post says new and updated apps must target API 37 (Android 17) from August 2027, removing the opt-outs for orientation and resizability on large screens.

On large screens (600 dp class), an app targeting API 37 gets these behaviours:

  • screenOrientation and setRequestedOrientation() orientation requests are ignored.
  • resizeableActivity is ignored.
  • minAspectRatio and maxAspectRatio are ignored.

Screens under 600 dp are unaffected, and apps categorised as games through android:appCategory are exempt. An app that opted out on API 36 only loses the opt-out once it targets 37.

If you fixed Tier 3 properly, most of this is already done. Compare it with the August 2026 target API 36 rule: that one was a version bump, this one changes how your layouts behave.

What changes for games?

Games follow a different clock for quality. Tier 3 (Ready) is required from August 2027, not April. The April screenshot rule still applies: at least 3 foldable screenshots and 1 phone screenshot, in the game's primary orientation. Apps need 2 phone screenshots, games need 1.

Game Tier 3 means full screen in supported orientations, HUD elements inside safe areas, clean in-engine letterboxing or pillarboxing in orientations you don't support, and state and touch alignment preserved across fold, unfold, rotation and multi-window. Google publishes separate game guidelines, so read those, not the app ones.

Whether to bundle API 37 with the April work

Our take: don't wait for the deadline to find out what fails.

  1. This month, run the Tier 3 tests on both emulators and file the failures.
  2. Fix them, starting with orientation locks and lost state.
  3. Capture the screenshots from the emulators and upload them.
  4. Ship one update well before April, so you learn whether Play Console accepts it while a rejection is still cheap.
  5. Put API 37 on the Q2 plan, and bundle it with the Tier 3 fixes if you're already editing the same manifests and layouts.

If you want more on the layout side, our Googlebook adaptive-app guidance covers the same quality tiers on desktop. For the next Android deadline after this one, follow our platform and language release notes.

FAQ

Will my existing app be removed from Google Play?

No. Existing un-updated apps stay downloadable. The consequence lands on your next update: an app that doesn't meet Tier 3 on foldables can't publish or update from April 2027, and may have reduced visibility.

Do I need a real foldable?

No. Google says screenshots from the Foldable (1:1 inner display) and Foldable (4:3 inner display) emulators are fully compliant, and the Tier 3 testing note names those same emulators.

Do games follow the same dates?

Partly. Games need 3 foldable screenshots and 1 phone screenshot from April 2027, but must meet Tier 3 from August 2027.

Does API 37 affect phones?

Only on large screens. The orientation and resizability changes apply at the 600 dp class. Screens under 600 dp are unaffected, and games are exempt through android:appCategory.

Sources

Share this article

Author Image

HighCircl Editorial Team

The HighCircl editorial team writes about hiring software engineers, nearshore development, and engineering team building. Our articles draw on direct experience sourcing and placing senior developers across Poland, Hungary, Slovakia, Serbia, Slovenia, Romania, and Spain — and on candid conversations with the CTOs and engineering leads who hire them.

HighCircl is a nearshore engineering network that delivers matched candidate shortlists in 72 hours. Every piece of content we publish is informed by real engagement data: actual developer rates, real hiring timelines, and what separates engineering teams that scale cleanly from those that stall.