Google has warned developers that next year Google Play will look more closely at how apps and games run on foldables and will offer more opportunities to showcase adaptive products. Specific store requirements are promised later this year. Until they appear, the best preparation is to understand what Google counts as adaptive quality and to fix weak spots now.

What is known today

In its October Android Dev Summit announcement, Google linked two things. First, with the arrival of Googlebook, apps can scale across phones and laptops without a separate codebase. Second, next year Google Play will look closely at how apps run on foldables. Details are promised "later this year", so there are no official requirements at the time of writing. For apps, Google advises following the Adaptive app quality guidelines; for games, a separate set of adaptive games guidelines.

Three tiers of adaptive quality

TierNameIn short
Tier 3 (basic)Adaptive readyThe app runs full screen or full window on all devices, without letterboxing or compatibility mode; basic support for keyboard, mouse, trackpad and stylus
Tier 2 (better)Adaptive optimizedLayout optimizations for all screen sizes and configurations, with enhanced support for external input devices
Tier 1 (best)Adaptive differentiatedAn experience designed for the device: multitasking, foldable postures, drag and drop, stylus

To earn the Large Screen Badge on Google Play, Google says to complete Tier 2 (optimize for all screen sizes) and Tier 1 (a differentiated experience for large screens). Google also notes that your app probably does not need to meet every requirement: implement the ones that make sense for your use cases.

How to test

According to Google, layout and UX testing should cover at least these device types:

  • Googlebook (160 ppi);
  • foldable (841×701 dp);
  • 8-inch tablet (1024×640 dp);
  • 10.5-inch tablet (1280×800 dp);
  • 13-inch Chromebook (1600×900 dp).

Android Studio provides emulators for this: Pixel Fold for foldables, Medium Tablet for tablets and Desktop (Preview) for desktop, which needs a Canary build. There is also the resizable emulator for arbitrary configurations.

What breaks first

Google states plainly that when screens fold, windows resize and apps move across form factors, usual layout assumptions can break and apps easily lose state. So your checklist should include:

  • State preservation when folding and unfolding, resizing the window and rotating.
  • Multi-pane layouts instead of a stretched phone screen (Grid, FlexBox, Navigation 3, WindowManager).
  • Tabletop posture for camera and media screens.
  • External input: keyboard shortcuts, hover states, tooltips, trackpad and mouse cursors.
  • Tablet and foldable screenshots on your Google Play listing: Google recommends showing the app on these devices and mentioning it in the description.

Speeding up work with agents

The updated Compose Adaptive skill helps agents turn compact screens into responsive multi-pane layouts and handle state and configuration changes. According to Google, it now adds foldable and desktop support: windowing, keyboard shortcuts, tooltips and trackpad hover states. The skill also audits Compose UI for these elements and refactors camera and media screens into tabletop layouts. It is a tool for a first-draft audit, but the result still needs manual checks on real devices.

Where to start in your project

  1. Find your current tier: go through the Tier 3 checklist and make sure the app does not run in compatibility mode.
  2. Run a critical flow on a foldable emulator while folding and resizing.
  3. Fix state loss before polishing visuals.
  4. Add keyboard and mouse support for the main actions.
  5. Update your store listing with large-screen screenshots.
  6. Watch for the Google Play announcement on requirements and opportunities for adaptive apps.

For more on technical approaches, see our article on tablet and foldable apps and our comparison of SwiftUI, Compose and classic Views.

Adaptivity is no longer a nice extra: it is becoming a visible quality signal in the store. Teams that start with state preservation and basic layouts will be ready before the requirements appear.

Sources: Android Developers Blog: Agentic and Flexible: A next era of Android development; Android Developers: Adaptive app quality guidelines; Android Developers Blog: Build for every screen with the latest Jetpack Compose updates.