Google Play Foldable Requirements: What Indie Android Developers Must Do by April 2027
A lot of Android apps still draw a phone-shaped box on a screen that has opened flat. Google Play foldable requirements put a month on that. On 18 November 2026, Mekka Okereke, GM, Google Play Apps, published the bar on the Android Developers Blog. From April 2027, an app has to meet the baseline Tier 3 adaptive quality guidelines for foldables, and the Play listing has to carry foldable screenshots.
Apps that miss the quality bar, the post says, “will no longer be able to publish or update on Google Play” and “may have reduced visibility on the store.”
Jay Peters at The Verge set the date next to Apple. The note landed weeks after Apple launched the iPhone Duo, which “already has more than 200,000 optimized apps.” The same day, @UniverseIce posted, and the post drew about 3.1K likes: “Google is finally FORCING Android developers to support foldables!”
Abner Li at 9to5Google and Android Authority covered the same post. This was written on 22 November 2026. The dates and the bar below are Google’s. The argument is from those reports, a Hacker News thread, a reader comment, and one indie developer who had just cleared a different Play rule.
What is Tier 3 “Adaptive ready” on Google Play?
Tier 3 is the line Google is making mandatory for foldables. The blog’s refresher is two sentences. “Apps must fill the available display area without letterboxing or compatibility modes.” And: “Apps must preserve state (scroll position, text input, media playback) during rotation, folding/unfolding, and resizing, while supporting multi-window environments.”
The label on that line is Adaptive ready. Above it sit two tiers the April deadline does not yet require.
Tier 2, Adaptive optimized, looks at multi-pane layouts and at basic support for a keyboard, mouse, trackpad, and stylus. Tier 1, Adaptive differentiated, looks at tabletop and book postures, and at further behaviour such as camera continuity and picture-in-picture. Google’s sentence for what comes after the baseline is exact: “Google Play’s quality framework will progressively expand to incorporate Tier 2 and Tier 1 standards across foldables, tablets, Googlebooks, and Android XR.”
Higher tiers are where the store treatment sits. The post says developers who build for them can unlock “premier store badging, editorial spotlighting, and enhanced merchandising.”
Peters reports that Google “plans to extend” the requirements to tablets and Googlebook laptops in “future phases.” That is the reporter’s wording for the later stages. The April rule in the blog is the foldable baseline.
The tests behind the name are on the Tier 3 guideline, last updated 19 November 2026. One note on that page matters for anyone who locked the manifest. The large-screen test, including the 1:1 and 4:3 foldable emulators, is meant to be run where the device can rotate even if android:screenOrientation is set, and can enter multi-window even if android:resizeableActivity is false. The app still has to fill the display and keep its state.
Google’s post names Jetpack Compose as a toolkit that can scale from a phone to a foldable. On Hacker News two days later, kodebach wrote the practical version: “For normal apps using Compose or Views that’ll be the case unless you’ve done something very odd.” A Flutter or React Native binary is held to the same published bar. These sources do not score either toolkit on its own. The check is the app on those two emulators.
Do I need foldable screenshots for Google Play?
You can add them now. From April 2027, a new app or an updated store listing has to include them. Google’s sentence is: “Providing foldable screenshots by April 2027 will become a standard submission requirement when publishing new apps or updating your store listing.”
The count is three foldable screenshots on top of the standard two phone screenshots. The formats in the post: at least one shot of a 1:1 unfolded inner display. For 4:3 foldables, one 4:3 unfolded shot and one 10:16 folded outer portrait. A 16:9 landscape phone screenshot is now an option beside the portrait phone shots. A 16:10 folded landscape shot is optional too. The shots can come from a phone in your hand or from the Android Emulator.
The capture guide maps those ratios to emulator profiles, foldable_1_1 and foldable_4_3, and it includes a one-line prompt for an agent. Uploads go in Play Console under Grow, then Store presence, then Store listings. Google says shots uploaded now will show on listings over the next few weeks.
hn_submit asked, on 20 November 2026: “If all apps support foldables by default why should I have to submit screenshots of my app running on a foldable?” The same comment calls the wider set of Play tasks a hoop: “the hoops they’re now forcing you to jump through are getting downright ridiculous.”
kodebach’s reply grants the annoyance and then the size of the task: “opening the emulator and taking a few screenshots (or telling your agent to do so) isn’t that hard.” He also wrote that “the basic requirement that applies to all apps is more or less just ‘the app fills the screen without black bars’.” And he argued the hard cases are games that draw with OpenGL or Vulkan and assume one aspect ratio: “This requirement is mainly about games and such that render directly with OpenGL/Vulkan and might assume a fixed aspect ratio.”
Taking the shots is the small half of his point. Shipping a first version with a coding agent is already ordinary, and the capture guide tells that agent which emulators to open. The quality bar is the half that fails if the app letterboxes, drops the text the user typed, or dies in a split window.
What happens if my app doesn’t meet the Google Play foldable requirements?
The quality sentence and the screenshot sentence do different work, and the milestone list adds a third line.
Miss Tier 3, and Google says the app will no longer be able to publish or update, and it may have reduced visibility. Leave an existing app un-updated, and the April milestone says “Existing un-updated apps will remain downloadable.” Update the store listing, or publish a new app, and the three foldable screenshots are part of that submission.
kodebach read the screenshot half this way: “Google also isn’t de-listing apps that don’t provide screenshots, they’re just not promoting them and you’ll have to add screenshots with your next update.” That sentence is his. It matches the “remain downloadable” line more closely than it matches the quality-bar line about publish and update. The two lines can sit together. An old build you do not touch stays up. A build you try to ship, or a listing you try to change, has to clear what Google required for that submission.
matteventu, commenting on Li’s piece, is waiting to see the enforcement: “Curious to see whether the requirements will actually be as strict as they make them seem (on paper).” The next sentence in that comment is about Google’s own catalogue: “If so, then also Google will have a ton of work to do to modernise all of their apps.”
When do the foldable requirements apply to games?
Games pick up the screenshots with everyone else, and they get a later month for the quality bar.
Peters wrote that similar requirements apply to games, with until August 2027 to be ready for Android foldables, while three foldable screenshots are still due on listings from April. Li reported the same split: foldable screenshots on game listings by April 2027, and Tier 3 large-screen quality in August 2027. Li’s account of that games baseline is specific. The title renders full screen in the orientations it supports, keeps the HUD inside safe areas, letterboxes or pillarboxes in the engine when rotated to an orientation it does not support, and keeps state and touch alignment through folding, unfolding, rotation, and multi-window resizing.
That August quality date is the reporters’ account. The blog points game developers to a separate large-screen page and, in its own August milestone, states a different requirement for apps in general: new and updated apps must target API level 37, Android 17.
kodebach’s OpenGL and Vulkan point is the reason a game studio would read April and August as two different jobs. A fixed aspect ratio is the case he thinks will fail a test whose bar is filling the screen. Google’s calendar, as Peters and Li report it, gives that category until August for the quality bar, and still asks for the three shots in April.
What a one-person Android app already owes Play
The foldable rule lands on a console that already makes a new personal account wait.
Play’s help page says personal accounts created after 13 November 2023 must run a closed test with at least 12 testers opted in continuously for 14 days before applying for production. App Store review times in 2026 already records a Hacker News comment describing that same gate, from a developer who found Google’s process the heavier of the two stores.
On 18 November 2026, the day of Okereke’s post, Sabahattin Kalkan published Fazor on Indie Hackers. Fazor is eleven offline electrical calculators, built with Kotlin and Jetpack Compose. He wrote: “Finding 12 testers took one day: my own network plus free tester communities.” Then: “Production access was granted the same day I applied.” And: “The production release was approved and live the same day too.” His summary of the cost is one line: “The rule cost me 14 days of waiting, not 14 days of work.”
That is his report of one approval. It is a Play hoop already in force for a solo developer who wants a production listing. The foldable quality bar is the next gate on a build you publish or update. The three screenshots join it when you publish a new app or change the store listing.
A portrait lock is the case to retest before then. The Tier 3 guideline tells you to run the large-screen test on a device that can still rotate when android:screenOrientation is set, and that can still enter multi-window when android:resizeableActivity is false. The app has to fill that window. In August 2027, new and updated apps have to target Android 17. Google’s line for that requirement is: “will require apps to target API level 37 (Android 17), removing developer opt-outs for orientation and resizability restrictions on large screens.”
A checklist before April 2027
Each step is a test or an upload path Google has already written down.
-
Read the Tier 3 guideline next to the 18 November post. The post is the deadline. The guideline is the test.
-
Run the app on a 1:1 foldable emulator and a 4:3 foldable emulator. The blog’s prep list names those two device types. The capture guide calls the profiles
foldable_1_1andfoldable_4_3. -
Rotate, fold, unfold, and resize. Check three things the blog names: scroll position, text in a field, and media playback. Each one should still be where the user left it.
-
Open the app in multi-window and use it. Tier 3 includes that window, including on a test device that enters split screen even when the manifest says the activity is not resizable.
-
Confirm the app fills the window. The failing look is letterboxing or a compatibility mode. kodebach’s short form, black bars, is the same failure.
-
Capture the listing set. At least one 1:1 unfolded inner display. For the 4:3 foldable, one 4:3 unfolded shot and one 10:16 folded outer portrait. Keep the two phone screenshots. Add a 16:9 landscape phone shot only if you want the new option. The capture guide has the pixel sizes and the agent prompt.
-
Upload under Grow, then Store presence, then Store listings. Uploads are open now. From April 2027 they are part of publishing a new app or updating the listing. A game listing owes the same three shots in April. Peters and Li put the game quality bar in August 2027. If you will still ship updates that August, target API level 37, Android 17.
A short timeline
| When | What is on the record |
|---|---|
| 18 November 2026 | Google publishes the adaptive quality standards. Foldable screenshots can be uploaded. The Verge, 9to5Google, and Android Authority report it. @UniverseIce posts. |
| 19 November 2026 | The Tier 3 guideline page shows a last-updated date of 19 November 2026. |
| 20 November 2026 | On Hacker News, hn_submit calls the screenshots a hoop. kodebach says the emulator work is small, and that filling the screen is the baseline. |
| April 2027 | Tier 3 for standard apps on foldables. Three foldable screenshots, plus two phone screenshots, when publishing a new app or updating the listing. Games owe the screenshots. Existing un-updated apps stay downloadable. |
| August 2027 | New and updated apps target Android 17, API level 37. The Verge and 9to5Google say games meet Tier 3 large-screen quality this month. |
The rules are Okereke's post and the Tier 3 guideline. Screenshots: the capture guide. Reporting: The Verge, 9to5Google, Android Authority. Voices: @UniverseIce, the Hacker News thread, and Sabahattin Kalkan on Fazor. The earlier testing gate is Play's 12-tester rule.
April is the month a standard app has to fill the foldable, keep its place when the screen changes, and show that on the listing. August is the month Google has named for Android 17, and the month Peters and Li name for game quality. An app you never touch stays downloadable. An app you still update has to clear the bar to ship the next one.
hn_submit called the new shots a ridiculous hoop. kodebach called them an emulator afternoon, and said a Compose or Views app already fills the screen unless something odd is going on. matteventu is waiting to see whether the paper rule is the rule Play enforces. Google’s reason for building past Tier 3 is the next expansion of the bar, and the store treatment that comes with it: premier store badging, editorial spotlighting, and enhanced merchandising.
What do you think? If you ship an Android app on your own, is this a weekend on two foldable emulators, or something you will leave until Play Console warns you?
FAQ
What is Tier 3 "Adaptive ready" on Google Play?
Tier 3 is the baseline Google Play will require for foldables in April 2027. On the Android Developers Blog on 18 November 2026, Mekka Okereke, GM, Google Play Apps, describes Adaptive ready this way. Apps must fill the available display area without letterboxing or compatibility modes. Apps must preserve state, including scroll position, text input, and media playback, during rotation, folding and unfolding, and resizing, while supporting multi-window. Tier 2, Adaptive optimized, covers multi-pane layouts and basic keyboard, mouse, trackpad, and stylus support. Tier 1, Adaptive differentiated, covers tabletop and book postures, camera continuity, and picture-in-picture. Google says its quality framework will progressively expand to incorporate Tier 2 and Tier 1 standards across foldables, tablets, Googlebooks, and Android XR. Building for those higher tiers is how developers keep up as the bar moves, and how they unlock premier store badging, editorial spotlighting, and enhanced merchandising. The written tests are on the Tier 3 adaptive app quality guideline, last updated 19 November 2026.
Do I need foldable screenshots for Google Play?
You can upload them now, and from April 2027 you need them when you publish a new app or update the store listing. Google's 18 November 2026 post says three foldable screenshots are required in addition to the standard two phone screenshots. The formats are at least one 1:1 unfolded inner display, and, for 4:3 foldables, one 4:3 unfolded screenshot and one 10:16 folded outer portrait. An optional 16:9 landscape phone screenshot is now allowed, and a 16:10 folded landscape shot is optional. Google's capture guide uses the foldable 1:1 and foldable 4:3 emulators, and screenshots can also come from a physical device. Upload them in Play Console under Grow, then Store presence, then Store listings. On Hacker News on 20 November 2026, hn_submit asked why screenshots are required if apps support foldables by default. kodebach replied that opening the emulator and taking a few screenshots, or telling an agent to do so, is not that hard.
What happens if my app doesn't meet the Google Play foldable requirements?
Google's 18 November 2026 post says apps that do not meet the quality bar will no longer be able to publish or update on Google Play, and may have reduced visibility on the store. The same milestone list says existing un-updated apps will remain downloadable. The three foldable screenshots become a standard submission requirement when publishing new apps or updating the store listing. On Hacker News on 20 November 2026, kodebach wrote that Google is not de-listing apps that do not provide screenshots, that those apps are not being promoted, and that screenshots are added with the next update. That is his reading of the screenshot rule. Google's sentence about publish and update is about the quality bar. A reader on 9to5Google, matteventu, wrote that they were curious whether the requirements will be as strict as they seem on paper.
When do the foldable requirements apply to games?
Games need the three foldable screenshots from April 2027, and the Tier 3 large-screen quality bar comes later. Jay Peters at The Verge, on 18 November 2026, wrote that games have until August 2027 for that quality bar, and that game listings still need three foldable screenshots starting in April. Abner Li at 9to5Google reported the same split. Li's account of the games baseline says a title renders full screen in the orientations it supports, keeps HUD safe areas clear, letterboxes or pillarboxes in-engine when rotated to an unsupported orientation, and preserves state and touch alignment across folding, unfolding, rotation, and resizing. On Hacker News, kodebach argued the baseline is mainly about games that render with OpenGL or Vulkan and assume a fixed aspect ratio. Separately, Google says that in August 2027 new and updated apps must target Android 17, API level 37.
What should a solo Android developer test before April 2027?
Test on a 1:1 foldable emulator and a 4:3 foldable emulator. Rotate, fold, unfold, and resize, and check that scroll position, typed text, and media playback survive. Open the app in multi-window and confirm it fills the window without letterboxing or a compatibility mode. The Tier 3 guideline says to run that test even where the manifest locks orientation or sets the activity as not resizable. Capture at least one 1:1 unfolded shot, one 4:3 unfolded shot, and one 10:16 folded portrait, on top of the two phone screenshots, and upload them before you next change the store listing after April 2027. Google's capture guide documents the emulator profiles. If the app is a game, the screenshots still start in April and The Verge puts the quality bar in August 2027. New and updated apps must target Android 17, API level 37, by August 2027, and Google says that target removes opt-outs for orientation and resizability restrictions on large screens.