Google Play Foldable App Requirements: April 2027 Rules Explained

On this page
Google Play foldable app requirements will make baseline adaptive layouts and dedicated screenshots mandatory for new apps and updates in April 2027. My main takeaway is practical: the larger screen has to protect the task you were doing, not merely display a larger version of the same page. Google announced the change on November 18, and it remains a significant platform story as developers plan their next release cycles. This is an analysis of the published requirements, not a report of hands-on testing.

Google Play foldable app requirements: the dates
| Milestone | Published requirement |
|---|---|
| November 2026 | Foldable screenshot uploads open in Play Console |
| April 2027 | Tier 3 adaptive baseline for standard apps; dedicated foldable screenshots for submissions |
| August 2027 | New and updated apps target Android 17, API level 37 |
| Existing apps | Unupdated apps remain downloadable under the announced April transition |
The distinction between a submission restriction and an immediate removal matters. Readers should not interpret the announcement as a promise that every awkward app disappears from their phone in April. Google describes a publishing and updating gate, alongside potential store-visibility consequences. Its official adaptive-quality announcement is the primary reference for the timetable.
Continuity is the feature users actually notice
Imagine composing a long reply on the outer screen, opening the phone to check a document, and discovering that the reply has vanished. That hypothetical failure is more consequential than an unattractive margin. It turns a hardware convenience into a risk. For a developer, the useful question is whether the application preserves the user’s intention through a change in available space.
A sensible review therefore starts with an unfinished task. Enter text, choose an attachment, move down a long list, or pause a video at an identifiable moment. Then change the window. Check the result against the original state, rather than deciding that the app works because it still launches. A screenshot can prove that a page fits. It cannot prove that the page remembers what matters.
This is also why a short demonstration should include an interruption. Real use involves a message arriving, a second application opening, or the keyboard taking over part of the display. A layout that looks convincing on an empty screen may become frustrating once a person starts working. The testing goal should be a completed task across those transitions.
The baseline is only the beginning of better layouts
Google’s Tier 3 baseline covers available display space, state continuity and multi-window support. Its higher tiers move toward better use of space and capabilities such as multi-pane interfaces and posture-aware experiences. The April baseline should not be confused with a demand that every application immediately implement every advanced foldable feature.
For a news reader, a single readable column can be a good decision. For an inbox, a message list beside the selected conversation may be more useful. The correct arrangement depends on the task. Adding panes simply to demonstrate that the screen is wide can produce smaller controls, competing focal points and additional navigation problems.
I would begin a design discussion by asking which information people repeatedly move between. That is the strongest candidate for simultaneous display. If a second pane merely repeats information already visible, the extra complexity needs justification. The value of a larger screen is reduced effort, not the number of rectangles a designer can fit inside it.
How a small team can prepare without a rewrite
First, identify the five journeys that generate the most value or the most support requests. A shopping application might choose search, product comparison, basket editing, checkout and order tracking. A reader might choose discovery, opening an article, adjusting text, saving a story and returning to a previous position. These are proposed planning examples, not a prescribed Google checklist.
Next, record observable pass conditions. A basket retains its contents. A draft retains its text. A filter remains selected. A document returns to the same location. Those conditions make failures easier to reproduce and give product managers a clear reason to prioritize work that may otherwise look like cosmetic maintenance.
Then separate layout defects from data-lifecycle defects. A button falling below the keyboard is a different problem from a form being recreated with empty fields. Keeping those issues distinct helps a team assign the right fix and verify it. A broad ticket labelled support foldables tends to conceal the actual work.
Finally, leave time for a second review after the fixes. Changing navigation or pane structure can alter focus order and the route back to a previous page. A successful repair should preserve accessibility and predictable navigation as well as appearance. The best evidence is a short, repeatable task recording accompanied by the device and window conditions.
Store screenshots become a separate release task
The announcement calls for three foldable screenshots in addition to the standard phone screenshots, covering the relevant inner and outer display formats. Teams should treat these assets as part of release preparation. Google says emulator captures can meet the requirement, which is useful when a team does not own every physical shape.
Capture screens that explain a real workflow. An empty dashboard says little about spacing under load; a populated example is more informative. Use clearly fictional sample data, remove personal information and keep the displayed features aligned with the version being submitted. Store artwork should help a prospective user understand the application they will actually receive.
For buyers, this policy is another reason to evaluate software alongside hardware. Our coverage of the vivo X Fold6 India release provides device context, while the Pixel 11 series announcement covers another part of the Android ecosystem. Neither a specification sheet nor a store badge replaces checking the applications you depend on.
Frequently asked questions
Do existing apps stop working in April 2027?
The announcement says existing unupdated apps remain downloadable. The April milestones concern submission requirements and the adaptive baseline for standard apps. That is different from remotely disabling installed applications.
Are games on exactly the same schedule?
Google links to separate requirements for games. Developers should consult that dedicated guidance rather than applying every standard-app milestone to a game without checking its scope.
Must a developer buy several foldable phones?
Google accepts compliant emulator screenshots and describes emulator testing as an option. Physical testing can still reveal handling and input issues, but the announcement does not make ownership of every listed device a screenshot prerequisite.
What should users check before buying a foldable?
Try the applications that matter most with an unfinished task, then change the screen or window. Preserved text, position and navigation are more useful evidence than a polished home screen alone.
