Google Will Require Android Apps to Handle Foldables From April 2027

From April 2027, Google will require Android developers to ensure baseline support for foldable devices, according to The Verge. Developers who do not meet the requirement risk being unable to publish or update their apps, or seeing reduced visibility on Google Play.
The benchmark is what Google calls "Tier 3 — Adaptive ready." Under that standard, an app must fill the available display area without letterboxing (the empty bars that appear when content does not fill the screen) or falling back to compatibility modes. It must also preserve state, meaning the scroll position, text input and media playback the app is holding in memory, through rotation, folding and unfolding, and resizing. Apps must support multi-window environments as well.
Games fall under similar foldables requirements, with a compliance deadline of August 2027. Game developers must still share three foldable screenshots for their app listings starting in April. Those screenshots are required of all apps as of the April 2027 deadline.
The two deadlines separate two different kinds of work. Listing assets are a production task that can be completed within a normal release cycle. Tier 3 compliance is an engineering task. Preserving scroll position, text entry and playback position through a fold event requires that application state survive configuration changes and that layouts reflow rather than restart. A team that treated foldables as a tablet variant with a different aspect ratio will find that the requirement concerns behavior under continuous resizing, not a fixed set of breakpoints (the screen widths at which a layout switches to a different design).
The broader context here is that the requirement moves foldable support from optional polish to a condition of distribution. Android runs across phones, tablets and foldables, and a common behavioral baseline is what makes a single codebase practical across that range.
In my view, the enforcement lever is what will determine how seriously teams take the work. Publishing access and listing visibility on Google Play give the requirement teeth, and the state-preservation criteria are where most of the engineering effort is likely to land.
What the requirement makes possible is a predictable experience. A user who unfolds a device mid-session should find the app exactly where they left it, with the same text in the field and the same video position. That sounds like a modest outcome, and it is the kind users notice mainly when it fails. A stated, enforced baseline gives developers a clear target and gives users a consistent result on hardware that is changing shape.


