If you've just gotten a foldable phone and are wondering how to adjust the aspect ratio of your apps so they don't look stretched or have black bars, you've come to the right place. The combination of new system policies, application-based adjustments, and good design practices It allows you to tame large internal displays, narrow external displays, and desktop window mode without losing quality or context.
In recent months, complaints have emerged from users of devices such as the Galaxy Fold and Pixel Fold: some apps are enlarged too much, others are distorted, and in games, the result can be inconsistent. Android 16, per-app screen settings, and an adaptive UI strategy They aim to correct that oscillation, whether you're a user who wants to force full screen in seconds or a developer looking for seamless continuity when folding or unfolding.
What's changing in Android 16 for large screens and aspect ratio?
When an app targets API 36, its activities are treated as resizable by default and can enter multi-window mode if the device meets the minimum width threshold. In that context, the system ignores attributes and APIs such as screenOrientation, resizeableActivity, minAspectRatio, maxAspectRatio and calls like setRequestedOrientation() with fixed orientation values that previously forced the UI.
Exceptions, temporary opt-out and publication schedule
There are exceptions to this model. These overrides do not apply to screens with sw < 600dp (Conventional mobile phones and many external screens on foldable phones) and games (according to the Android:appCategory=game brand) are excluded. Furthermore, if the user enables the app's original behavior for aspect ratio in the settings, that preference takes precedence.
If for justifiable reasons you need to disable this behavior in API 36, there is a supported manifest property. You can declare it by activity or at the application level to allow specific size restrictions while migrating to a responsive UI.
<activity ...>
<property
android:name="android.window.PROPERTY_COMPAT_ALLOW_RESTRICTED_RESIZABILITY"
android:value="true" />
</activity>
<application ...>
<property
android:name="android.window.PROPERTY_COMPAT_ALLOW_RESTRICTED_RESIZABILITY"
android:value="true" />
</application>
Keep the horizon in mind: In API 37, disabling this behavior on screens with sw ≥ 600dp will no longer be allowed.For their part, the stores set their own deadlines; Google Play will require target API 36 from August 2026, so it's advisable to plan the transition in advance.
Quick settings for users: aspect ratio per app and density
If you're more practical and want results now, check your brand's system settings. On many devices you will find “Full screen apps” or “App scaling” In Settings > Display, you can force an app to fill the entire available surface or stay within a narrower frame.
On some foldable phones, you'll also see a contextual button that switches to full screen when it detects 16:9 content. The problem is that sometimes there isn't a quick reverse gesture to return to 16:9, and apps like Instagram can behave strangely when switching to full screen.
If you need to fine-tune it further, you can change the "Smallest width" (logical density) from the Developer Options. Increasing that value makes everything look smaller; lowering it makes it look bigger.Make incremental changes and note the original value so you can revert if you're not happy with the adjustment.
Google has also driven improvements in app expansions. Android 14 QPR1 introduced the ability to enlarge applications individually onto large screens (confirmed by leakers such as Mishaal Rahman), making it easier to remove black bars on Pixel Fold and Pixel Tablet; in Android 15, its widespread presence on large screens is expected unless the manufacturer decides otherwise.
Real voices: when your app looks weird on a Fold
Some Galaxy Fold users are reporting that Instagram and Reddit appear too enlarged or stretched, and that games look bad or are excessively zoomed in. Some are even considering returning the device because the internal screen seems to worsen the experience instead of improving it, despite being designed so that videos don't cover the entire surface.
Disappointments with the camera or battery are also mentioned in some scenarios, although the most significant issue is the compatibility of third-party apps. The recurring question is whether there is a setting that forces aspect ratio or full screen. without having to go app by app, and if there are shortcuts or third-party apps that make the switch "on the fly." Currently, the system offers per-app controls and contextual buttons, but there isn't always an immediate universal switcher.
Android technical fundamentals: continuity, states and postures
For everything to flow smoothly when folding and unfolding, you have to think in terms of states and positions, not just fixed sizes. ViewModel, Jetpack Navigation and onConfigurationChanged They are the basis for continuous experiences that do not lose context when switching from external to internal screen.
Screen continuity is the essence of a foldable phone: if you're reading an email on the cover and unfold the phone, Ideally, the message details should be displayed alongside the list. in a two-panel interface. With ViewModel, the UI state (selected item, scroll, forms) survives configuration changes, and with single-activity navigation, you change fragments according to the actual space.
Forget "guessing" physical sizes and work with real metrics. WindowMetrics and Jetpack WindowManager tell you the effective window area, very useful in multi-window and desktop environments, where the usable region may differ from the physical screen.
Types of folding mechanisms and design: hinge, positions and 12L
There are book-type designs (Z Fold, Pixel Fold), clamshell type (Z Flip) and even dual screen (Surface Duo). The hinge introduces areas to avoid. For critical elements, take advantage of the improved support in Android 12L and later to adapt layouts based on fold and size classes.
For two panels in classic views, SlidingPaneLayout facilitates proper separation, and ConstraintLayout helps content flow without absolute positions. Remember to declare android:resizeableActivity=true (or assumes the default value in API 36+ on large screens) and tests the emulator's foldable presets to validate postures.
Compose and Window Size Classes: a UI that doesn't break
Jetpack Compose simplifies adaptive design. Window Size Classes (Compact, Medium, Expanded) They allow you to decide when to show one or two columns, enlarge fonts, or change a list to a 2-3 column grid without being tied to specific devices.
In the root composable, get the size class and propagate it as a derived state. Avoid conditioning internal components on "is it a tablet?"The app can run in multi-window mode or on an external monitor with atypical dimensions.
BoxWithConstraints is useful for alternating representations depending on the available space. Do not defer data loading based on sizeIt passes all the information to the component and decides what is displayed, minimizing side effects when resizing.
In terms of status, it raises flags like showMore to the top level and uses rememberSaveable when it needs to survive recreations. Move the heavyweight initialization to the ViewModel's init. so that it doesn't happen again with every configuration change.
Avoid stretching, enable scrolling, and take care of the camera.
If a design doesn't scroll horizontally, you can "lose" buttons outside the viewport. Enable scrolling where appropriate and verify accessibility with large font sizes and screen readers. Keep libraries and APIs up to date, including support for Android 16.
Camera previews that assume fixed orientation or ratio may appear stretched or reversed. Ensure the visor rotates correctly and adjusts UI aspect ratios different from those of the sensor.
Tests on emulator and real devices
To validate the changes in Android 16, use Pixel Tablet and Pixel Fold emulators in Android Studio and enable targetSdkPreview= "Baklava" in your module. You can also activate UNIVERSAL_RESIZABLE_BY_DEFAULT from the compatibility framework to simulate universal resizing behavior.
Automate with Espresso and Jetpack Compose's test APIs; with UI Automator you can check elements in different positions. Test transitions: during video playback, switch between one and two columns and ensure that there are no state losses or unexpected closures.
Device farms are allies if you don't have hardware. Firebase Test Lab and Samsung Remote Test Lab They give you access to real equipment on demand and CI/CD integration to detect nightly regressions.
Web modeling for foldables: CSS, segment APIs, and performance
On the web, foldable phones require more than just classic breakpoints: you need to consider aspect ratio and screen segments. Combine media queries by width with aspect ratio and reorganizes menus, grids, and images in real time.
@media (min-width: 600px) and (max-width: 900px) {
/* Intermedias: plegable semiabierto */
}
@media (aspect-ratio: 3/4) {
/* Vertical plegado */
}
@media (aspect-ratio: 16/9) {
/* Apaisado desplegado */
}
If the browser supports it, the Window Segments API helps detect active segments for multi-panel UIs. Complement with viewport-fit: cover for rounded corners and detects the orientation from JS without unnecessary reflows.
if (window.screenSegments) {
const segments = window.screenSegments;
console.log(segments);
}
/* CSS */
body {
viewport-fit: cover;
}
/* JS */
if (screen.orientation.type === 'landscape-primary') {
console.log('Modo apaisado');
}
Performance rules: use lazy loading, compression, and Lighthouse/WebPageTest to trim bottlenecks. In multitasking with foldable websites, a slow website is abandoned sooner., especially when competing with well-optimized native apps.
Wear OS: micro-interactions that deliver value in seconds
In watches like the Galaxy Watch or Pixel Watch, short interactions are key. Prioritize Tiles, complications, and notifications to display essential data and open the app with a tap when needed.
Compose for Wear OS and components like ScalingLazyColumn help on small and curved screens. Design with ambient mode and battery life in mind.It reduces network calls and relies on Health Services for sensors. Wear OS 6 incorporates Material 3 and improved AI integration for contextual responses.
Complications should deliver a unique relevant piece of information (next appointment, unread messages) and Tiles quick actions (play/skip, steps). ComplicationSlotsManager It allows the user to add your data to their favorite sphere.
Typical mistakes that ruin the experience
With the push of Android 16, the classic flaws are more noticeable. Don't ignore the hinge in the layoutDo not block orientation without cause, avoid components that occupy the entire width without limits, and do not forget the scroll where height may be lacking.
In wearables, keep the UI simple and accessible, with generous touch targets and basic gestures. Update libraries and API levels regularly. and check compatibility with screen readers and large font sizes.
Strategy and partners to accelerate
Optimizing for foldable and wearable devices is not about duplicating work, it's about adopting smart and adaptive architectures. Teams with experience in AI, cybersecurity and cloud (AWS/Azure) They can accelerate delivery while maintaining performance, security, and scalability.
For example, Q2BSTUDIO positions itself as a partner to build custom apps and software that leverage dynamic displays, AI agents, and advanced analytics. They integrate business intelligence and Power BI So that the product not only works, but also generates actionable insights. If you're looking for custom development or cybersecurity consulting, their proposal covers everything from strategy to implementation.
Pixel Community and Ecosystem
If you're into forums, the Samsung Galaxy Fold community brings together news, reviews, tips, and discussions about foldable phones in general. Participate respectfully, add your flair, and report content that violates the rules. to maintain a good environment.
In the Pixel ecosystem, the Pixel Fold opts for a 6:5 format that, when unfolded, almost feels like a tablet in a slim body. The Pixel Tablet includes a 10,95-inch LCD panel with a resolution of 2560×1600And the Pixel family received new features such as Video Boost and Night Sight for video, in addition to camera improvements, USB webcam mode in recent models, document cleanup, and privacy advancements.
Mastering aspect ratio and resizing in foldable apps means accepting the new model: Let the system handle large screens, build responsive UIs, preserve state, and test in real-world scenariosIf your device isn't performing as expected and you're considering upgrading, there are buyback and resale options—services like Moviloff have been mentioned—to give your device a second life.
Meanwhile, per-app adjustments, smaller width control, and the adoption of Android 16 practices will allow you to enjoy more visible content, less distortion, and an experience worthy of your screen. Share this information and more people will know how to configure their foldable phone and improve the aspect ratio.
