The Android universe no longer fits into a single screen mold. Phones, tablets, foldableChromeOS, cars, TV, and XR coexist with very different sizes, orientations, and usage contexts. This range brings good news for your users and a technical challenge for your team: designing interfaces and logic that fit like a glove regardless of the canvas. Below, learn how to change the aspect ratio of apps on these devices.
What changes with Android 16 on large screens sw600dp?
For apps targeting API level 36, Android 16 imposes a coherent model of adaptive design. which ignores several traditional restrictions when the device falls into the large-screen category. This affects tablets, large internal screens of folding phones and desktop window mode.
- Ignored attributes On screens with a width smaller than or equal to 600 dp: screenOrientation with values ​​such as portrait or landscape, resizeableActivity, minAspectRatio and maxAspectRatio.
- Orientation-related methods such as setRequestedOrientation and getRequestedOrientation they are also neutralized for fixed orientation values.
- In this context, API 36 target apps are resizable and enter multi-window, equivalent to having resizeableActivity set to true when sw is greater than or equal to 600 dp, without needing extra adjustments.
This approach standardizes behavior and reduces UI surprises on large screens. User experience takes precedence over forced closures to a particular orientation or aspect ratio.This involves reviewing old assumptions in layouts and views.
Exceptions and special cases regarding adjusting the aspect ratio
There are situations in which the system maintains the previous behavior. The main exceptions These cancellations are:
- Screens with less than 600 dp sw, where the usual manifest restrictions are still respected in most phones and external screens of some foldable phones.
- Games identified with the appCategory manifest brand as game, provided they are distributed with Android App Bundles and Play app signing.
- If the user forces the app's default behavior in the device settings for aspect ratio, that preference takes precedence.
How to temporarily disable cancellations?
If you need time to adapt, you can disable this new behavior on a per-activity or app-level basis. Declare the ownership of the manifest android.window.PROPERTY_COMPAT_ALLOW_RESTRICTED_RESIZABILITY and thus you request to keep the old restrictions on large screens.
- In an activity element, add a property with name android.window.PROPERTY_COMPAT_ALLOW_RESTRICTED_RESIZABILITY and value true for that specific activity.
- The application element replicates the same property if you want to apply the behavior across the entire app.
Important: This is a safety net with an expiration date. At API level 37, the framework will eliminate this possibilityTherefore, in later versions, the restrictions will always be ignored on screens with a sw greater than or equal to 600 dp.
Testing and development environment
To verify the impact of these changes, Use the Pixel Tablet and Pixel Fold emulators in Android StudioConfigure your targetSdkPreview module with the value Baklava to start validating.
- On real devices, activate the UNIVERSAL_RESIZABLE_BY_DEFAULT flag within the app compatibility framework to simulate the new behavior.
- Automate interface testing with Espresso and Jetpack Compose test APIs, covering rotations, window resizing, folding and multi-window.
- If you don't have a diverse physical infrastructure, rely on device farms like Firebase Test Lab or Samsung Remote Test Lab for on-demand testing and continuous integration.
Common problems and how to solve them
When an app assumed a fixed window, The leap to big screens and folded postures can bring to light several flaws:
- Components that stretch without limit horizontally or vertically. Add maximum widths and containers that limit expansion to maintain pleasing proportions.
- Designs without scrolling that hide buttons or fields horizontally. Activate scrolling where appropriate and validate accessibility with different window heights.
- Camera viewfinders with a rigid aspect ratio. Make sure you rotate the preview correctly and that The viewer adapts to the UI aspect ratio different from that of the sensor.
- Loss of state with resizing or rotation. Maintain state with ViewModel, rememberSaveable in Compose, and state lift patterns. avoiding destructive recreations.
- Static size assumptions. Model the UI with Window Size Classes and adopt responsive layouts that react to frequent changes.
Responsive and adaptable design in folding books
A responsive design ensures that the app looks good on many sizes, but with foldable devices, you need to go further. Adaptive design allows for optimized variants for folded screens and deployed, or positions like table and book.
When unfolded horizontally, a large-screen foldable behaves like a tablet. A two-panel pattern with a navigation rail Take advantage of the spaciousness. Folded, a single-column layout with a bottom bar works cleanly and directly.
The devices fold inwards or outwards, and the fold can be flexible or a hinge with occlusion. Note that occlusionType FULL is used on dual-screen devices. such as some formats, where content should not be painted in the hinge area.
- Typical states: FLAT fully open and HALF_OPENED somewhere in between.
- Positions in HALF_OPENED: table position when the fold is horizontal, and book position when it is vertical.
- Avoid controls near the crease, place dialogs and pop-up menus outside the occlusion zone, and distribute content in left and right or top and bottom areas depending on posture.
To get started with a simple responsive design in Compose, BoxWithConstraints lets you adapt content to the available space. available, and then scale up to richer variations by posture.
Window size classes and Compose
Before discussing thresholds, let's refresh our units: px represents physical pixelsdp scales by density, and sp adds user settings, ideal for typography. Work with dp and sp to ensure your UI looks consistent across different densities.
The recent ecosystem recommends classifying windows into three sections. In width and height, Compact, Medium and Expanded They cover most cases:
- 0 to 599 dp Compact, typically vertically mobile.
- 600 to 839 dp Medium, vertical folding mobile or vertical tablet.
- 840 dp or more Expanded, mobile in landscape, foldable in landscape or tablet in landscape.
With the Material 3 window size class library, calculateWindowSizeClass returns a picture of the current size to decide on layouts. If you prefer total control, implement your rememberWindowSize and categorize width and height with your own limits.
This classification allows you to define patterns as a list in Compact and grid with variable columns in Medium and Expandedas well as increasing font sizes or paddings where it makes sense.
Manifesto, free size change and continuity
Many older apps carry three problematic lines: maxAspectRatio limited, resizeableActivity set to false, and screenOrientation locked. Removing them is the first step towards healthy, free-flowing behavior, and fundamental with Android 16.
Observe configuration changes with LocalConfiguration in Compose or the onConfigurationChanged callback in views, to understand how screenWidthDp, screenHeightDp, and orientation vary while the user resizes or rotates.
Also monitor the Activity lifecycle. In significant resizing, the activity can be recreated Since API 24, but not in minor changes. It adds a LifecycleEventObserver to see which events are triggered when minimizing, bringing back to foreground, and resizing.
In Compose, remember retains state between recompositions but not between activity recreations. rememberSaveable supports storage in savedInstanceState and avoids losing, for example, the expansion of a header or the scroll position after resizing.
When you raise state to the ViewModel, put heavyweight initialization in its init. You will avoid repeating network calls or file ES calls if the activity is destroyed and created multiple times during free-form testing.
Multi-window, drag and drop, and productivity
On large screens, Android 12 and higher use multi-window by default. The apps coexist in split screen and desktop window mode where they move and resize as on a traditional desktop.
This context unlocks powerful flows like drag and drop between apps. Implement the drag and drop framework to move images, text or files with natural gestures and integrate into real productivity scenarios.
Tools, SDKs and ecosystem
Jetpack Compose is today's modern bet for declarative UI. Its reactivity makes it easy to hear changes in window and posture., compose variants and preserve state.
Flutter has made progress in support for foldable devices, enabling native apps for Android and iOS with consistent adaptive interfacesIn addition, Samsung offers a dedicated SDK for Galaxy foldables with simulators and emulators to validate screen modes before release.
If you work with classic resources, remember the family of densities ldpi, mdpi, hdpi, xhdpi, xxhdpi and xxxhdpi. Vectors help reduce matrices by density., and the qualifiers by size and orientation remain valid for specific cases.
Real-world example: Google Wallet redesign for foldable devices
One popular app that has made the leap is Wallet. In Fold-type folding devices, with an aspect ratio close to 4:3Its UI evolved from an unhelpful expansion of cards to a two-panel scheme that makes better use of space.
Now the payment card selector is in one column, and the loyalty cards occupy the other half with vertical scrolling. Elements return to natural sizes instead of expanding to ridiculous proportions.And although there is a visually emptier area, readability and control are clearly improved. This type of decision exemplifies the adaptive design philosophy: prioritizing structure and hierarchy over filling pixels.
Practical tips for those using a recently launched folding laptop
If you notice apps enlarged or stretched on a modern Fold, go into the device's per-app aspect ratio settings. Some layers allow you to force full screen or a specific aspect ratio.The impact varies depending on the app. Remember that in Android 16, users can enable the app's default behavior in the aspect ratio settings, which will affect the final result.
Even so, the ball is in the developer's court. When the app adopts responsive designs and retains stateThe experience of unfolding, rotating, or separating windows ceases to be a pain and becomes an addictive bonus.
Camera, continuity, and details that make the difference
Camera previews usually assume a fixed aspect ratio. On non-compliant screens, images may appear stretched or inverted.Make sure to rotate the viewfinder with changes in orientation and allow viewfinders that adapt to UI ratios different from that of the sensor.
Continuity is crucial when moving from the outer screen to the inner screen. If the user opens an email in the small panelWhen expanded, you should display the list and details in two panels without losing focus. Keep text in fields, keyboard status, scroll position, and media playback where it left off.
Publication schedule and requirements
In Android 16, during 2025, Compatibility with all orientations, aspect ratios, and resizing becomes the benchmark for large screens for target apps API 36, with the possibility of temporarily disabling it as explained.
API target dates vary by store, but Google Play has set a general timeline: Starting in August 2026, it will require target API 36It's best to plan the migration now to ensure timely testing, redesigns, and state improvements.
Beyond foldable phones: Wear OS and other displays
Although the focus here is on foldable watches, the principle is the same for watches. In Wear OS, glance interaction reigns supreme.With Tiles, complications, and compact notifications that deliver value in seconds, not minutes.
Compose for Wear OS and Material 3 help with components like ScalingLazyColumn for curved surfaces. Optimizes battery and performance Minimize network and processing overhead, and leverage the Health Services API for sensors. In design, prioritize large touch targets, simple gestures, and voice.
The dynamic display market is undergoing a clear evolution. Android 16 pushes apps to abandon fixed orientations and aspect ratios On large screens, multi-window use cases, folded positions, and drag-and-drop functionality are no longer eccentricities, but expectations. With a responsive design based on Window Size Classes, a state-preserving architecture, realistic testing, and attention to details like the camera, your app goes from being stretched awkwardly to feeling native on any canvas, creating experiences that are truly enjoyable to use. Share this guide and more users will know how to adjust the aspect ratio of their apps on Android.