Image Not FoundImage Not Found

  • Home
  • Devices
  • Google Play will require foldable-ready Android apps by April 2027, turning adaptive design into a release gate
A developer sits at a desk using an open foldable phone next to a laptop in a softly lit office.

Google Play will require foldable-ready Android apps by April 2027, turning adaptive design into a release gate

Google is turning foldable support from a best practice into a store rule. In a post on Android Developers, the company said that starting in April 2027, apps on Google Play must meet at least Tier 3, “Adaptive ready,” of its adaptive app quality guidelines for foldables. Apps that miss that baseline will no longer be able to publish or update through Google Play, and they may also see reduced store visibility.

That matters less because of the screenshot requirement that arrives at the same time, and more because Google is using Play distribution as the enforcement tool. The real question for developers and device buyers is whether this is a necessary fix for a long-running Android weakness on larger screens, or a new recurring release cost imposed before foldable demand is big enough to justify it.

The short answer is both. Google is clearly trying to solve a genuine user-experience problem: too many Android apps still behave like fixed phone canvases when the screen changes shape. But it is solving that problem with the most powerful lever it has, which means the engineering and testing burden lands on developers first, even though Google has not published foldable-only usage figures, likely conversion gains, or expected compliance rates.

A Play policy, not just a design recommendation

Tier 3 is a baseline compatibility bar. Google says apps at that level must fill the available foldable display without letterboxing or compatibility modes, preserve scroll position, text input and media playback through rotation, folding, unfolding and resizing, and support multi-window environments. In practical terms, that targets the most visible failures: stretched or boxed phone UIs, broken state when a device changes posture, and apps that fall apart when users try to split the screen.

By attaching those requirements to publishing and updates, Google is converting a UI goal into a release gate for one of Android’s main distribution channels. That is the most consequential part of the announcement. Existing apps that are already on the store and remain unupdated after April 2027 will still be downloadable, so this is not a mass removal event. But unsupported apps could slowly stagnate as bug fixes and new versions stop shipping, and reduced visibility could make them harder to find.

There is a second deadline behind the first. In August 2027, new and updated apps must target API level 37, Android 17. Google says that change removes developer opt-outs for orientation and resizability restrictions on large screens. For teams that still assume a locked phone viewport, that is the point where temporary avoidance strategies begin to disappear.

Games have a different timetable. Under separate guidance, games get until August 2027 for the Tier 3 large-screen quality standard, though the foldable screenshot requirement still begins in April. That split matters because it changes the compliance calendar for studios, and because game rendering and layout problems are often different from productivity or social apps.

Baseline compatibility is not the same as a great foldable app

Google’s new floor is not the same thing as a premium foldable experience. Tier 3 is about not being broken. The more distinctive foldable and large-screen behavior sits above it.

Tier 2 evaluates responsive multi-pane layouts and basic support for keyboard, mouse, trackpad and stylus input. Tier 1 goes further, looking at tabletop and book postures, camera continuity, interactive picture-in-picture and multi-instance support. Google says apps that hit those higher tiers can receive badging, editorial spotlighting and enhanced merchandising.

That incentive structure is revealing. Google is separating compatibility from differentiation. Tier 3 is the minimum price of admission; Tier 1 and Tier 2 are where developers can make foldables genuinely useful and potentially win more prominent placement.

The company also frames the opportunity broadly. It says its adaptive framework spans more than 580 million large-screen devices in users’ hands today. But that figure includes foldables and other large screens, not foldables alone, so it does not answer the question many smaller developers will ask first: how many of my users actually need this work right now?

That missing denominator is why the economics will look very different across the market. A big consumer app with tablet ambitions may treat adaptive compliance as overdue housekeeping. An enterprise team with a fixed workflow, a small paid utility, or a contract shop maintaining several narrow-purpose apps may see mostly cost: layout refactoring, state-management fixes, multi-window testing, emulator or device coverage, three new foldable screenshots, and then an API 37 roadmap a few months later.

Who pays for coherence on Android’s expanding screens

Google’s argument is easy to understand even without internal numbers. Android has spent years expanding across new form factors, and inconsistent app behavior is one of the main reasons new device categories feel unfinished. A stronger baseline should reduce the familiar large-screen experience where an app looks like an awkward phone port. For buyers of foldables, that is tangible value.

But the company is also externalizing part of the cost of making that ecosystem coherent. The announcement does not say how automated enforcement will verify every state-preservation or multi-window requirement, whether exceptions exist, or how severe visibility penalties might be in practice. It also does not estimate engineering hours for a typical small app, or show whether the resulting user lift will outweigh the work.

That uncertainty makes the policy feel stricter than the evidence Google has made public. The Verge, which independently reported the mandate, connected the timing to Apple’s expected foldable plans, but Google itself does not present the move as a competitive reaction. What it has documented is simpler and more durable: Play will now be used to raise the minimum quality bar for adaptive behavior.

For developers, the immediate checklist is clear even if the return is not. Test what happens when an app rotates, folds, unfolds, resizes and enters multi-window. Remove hard-coded orientation or letterbox assumptions. Verify that scroll position, text input and media playback survive transitions. Prepare three foldable screenshots for the Play listing. Budget for API level 37 by August 2027. And watch for Play Console guidance as Google clarifies how enforcement will work.

For device buyers, the practical effect will be gradual rather than dramatic. Existing apps will not suddenly vanish in April. The likely change is slower but still meaningful: fewer brand-new or freshly updated apps should arrive on foldables in a boxed, brittle state, while developers that do invest beyond the baseline may become easier to spot through Play badging and editorial placement.

Google says this framework will later expand to tablets, Googlebook laptops and Android XR, though it has not published a full timetable. That makes this foldables policy look less like a one-off cleanup and more like the start of a broader compliance program for Android’s larger screens. The bet is that better baseline behavior will make the ecosystem healthier. The risk is that some developers will absorb a new release cost before they see enough users on those devices to make the math work.