ArticleAndroid
Android Developers · Google
Google’s adaptive quality framework distinguishes basic full-window support, optimized layouts and experiences that use device-specific features. Its checklists cover foldable postures, multitasking and external input, with linked tests and a device matrix. Developers can select the requirements that apply to their app rather than treating every guideline as universal.
Read the original →ArticleAndroid
React Native Docs · React Native
React Native’s Dimensions reference explicitly warns that folding can change window and screen size after startup. It recommends useWindowDimensions for React components, or a change listener where Dimensions is needed, so rendering does not keep stale cached values. This covers resizing inputs rather than hinge geometry or device-specific fold APIs.
Read the original →ArticleAndroid
Flutter API · Flutter
Flutter’s MediaQueryData reference explains how display features describe hinges, creases and cutouts in the coordinate space spanning the active screens. Feature type distinguishes an obstruction from a fold, while feature state exposes posture. The documentation explicitly limits this populated list to Android, so this entry does not imply equivalent iOS or HarmonyOS behavior.
Read the original →ArticleAndroid
Flutter API · Flutter
Flutter’s DisplayFeatureSubScreen places content in a sub-screen that avoids an obstructing display feature or half-open fold. It chooses the region nearest anchorPoint, with a Directionality fallback, and adjusts the child’s MediaQuery coordinates and padding. This complements the existing display-feature reference; hardware feature data is currently populated on Android.
Read the original →ArticleAndroid
Android Developers · Google
Google’s Camera2 guide explains how folding can change the active physical sensor behind a logical camera, including its orientation and lens facing. It recommends monitoring the active physical ID and re-reading camera characteristics instead of caching them, then updating preview transforms when the sensor changes. CameraX remains the suggested default when low-level Camera2 control is unnecessary.
Read the original →ArticleAndroid
Android Developers · Google
This foldable-specific quality checklist pairs posture, camera and multitasking requirements with named tests. It covers controller placement in tabletop mode, front and back camera previews, picture-in-picture, attachments and multiple app instances. The detailed scenarios complement the broader adaptive-quality tiers already in the Kit.
Read the original →ArticleAndroid
Android Developers · Google
Google’s Compose recipe explains how folding or resizing can disrupt scroll position and the state of individual list items. It uses rememberLazyListState() for list position and rememberSaveable for stateful elements such as text inputs. The example separates list-level state from item-level state so an unfolding transition can preserve both.
Read the original →ArticleAndroid
Android Developers · Google
Google explains window bounds, lifecycle callbacks and access to shared resources when apps run alongside one another. Its multi-instance section specifically describes how folding a device can background or terminate one of two app instances. WindowMetrics, multi-window callbacks and the verification checklist help separate resizing behavior from single-window pane layouts.
Read the original →ArticleiPhone Duo
Apple Developer · Apple
Apple’s AVFoundation walkthrough contrasts automatic switching through the virtual front camera with custom selection using AVCaptureDeviceDirectionCoordinator. It explains coordinating cameras relative to each display’s view as the device opens or closes. Preview aspect ratio, placement and rotation guidance completes the camera-specific adaptation path.
Read the original →ArticleiPhone Duo
Apple Developer · Apple
Apple covers split-view multitasking, multi-scene availability and supplementary UI across Duo’s displays. The talk shows onHingeChange for interactive effects and CameraCaptureAccessory for a camera’s outer-display content, with availability callbacks. It separates hinge-driven effects from layout decisions based on arrangement and region APIs.
Read the original →ArticleiPhone Duo
Apple Developer · Apple
Apple explains how navigation, toolbar and tab items share a vertical bar region on Duo. The talk covers system navigation containers, semantic item ordering, titles and symbols, and AxisBehavior for custom representations. Overflow and visibility-priority sections show how to keep important actions available as the bar changes layout.
Read the original →ArticleiPhone Duo
Apple Developer · Apple
This Apple Tech Talk explains displacement patterns for moving or resizing existing content around fold and camera regions. It introduces SwiftUI ArrangementView and UIKit arrangements for split and overlay presentations, including when standard navigation or scrolling containers are more appropriate. Examples connect active reserved regions to contextual, reachable controls.
Read the original →ArticleHarmonyOS / OpenHarmony中文
OpenHarmony Documentation · OpenHarmony
OpenHarmony’s Camera Kit guide explains how the available cameras can change when a device folds. It shows listening through CameraManager or display APIs, querying getSupportedCameras() again and selecting a camera that exists in the new state. Its ArkTS example coordinates XComponent recreation with camera switching to avoid leaving the previous preview on screen.
Read the original →ArticleHarmonyOS / OpenHarmony中文
OpenHarmony Documentation · OpenHarmony
OpenHarmony’s FolderStack reference documents moving selected child components above the crease through upperItems, along with fold and hover callbacks. It records Stage-model and device constraints, automatic-rotation behavior and a warning that an if/else parent disables the hover capability. Per-interface API versions make those limits visible beside the usage contract.
Read the original →ArticleHarmonyOS / OpenHarmony中文
OpenHarmony Documentation · OpenHarmony
The atomicService section of OpenHarmony’s module.json5 reference defines the resizeable option for adapting service windows when a foldable opens or closes. The option starts at API 20, defaults to false, and applies only when the app bundle type is atomicService. This is a narrowly scoped configuration requirement, not a replacement for adapting the actual layout.
Read the original →ArticleHarmonyOS / OpenHarmony中文
OpenHarmony Documentation · OpenHarmony
OpenHarmony’s display reference documents fold status, display mode and crease-region APIs, with per-interface version requirements. It distinguishes foldStatusChange, which tracks physical folding, from foldDisplayModeChange, which follows the resulting display mode. The foldability notes also describe devices whose auxiliary outer screens are not available for application customization.
Read the original →ArticleHarmonyOS / OpenHarmony中文
Huawei Developer · Huawei
Huawei’s AppAnalyzer rule catalog describes layout, rotation and continuity checks for HarmonyOS foldables. Its opening/closing continuity rule looks for lost input, changed scroll or playback position and unexpected page changes. The UX table marks continuity and orientation checks as available from tool version 26.0.0 for listed API 20+ foldable phones and emulators. Older sections have separate version limits; these are checking criteria, not evidence that an app has passed them.
Read the original →ArticleHarmonyOS / OpenHarmony中文
Huawei Developer · Huawei
Huawei documents the DevEco Studio emulator controls for switching foldable devices between folded, expanded and hover states; hover mode displays the crease avoidance region. The table also maps tri-fold controls to fold-status values and marks additional Mate XT controls as available from 6.1.0 Beta2. This is a HarmonyOS tooling reference, with device-specific restrictions, rather than evidence that an app has passed adaptation tests.
Read the original →ArticleAndroid
Android Developers · Google
This codelab adapts a legacy multi-activity app to a two-pane layout using XML rules or Jetpack WindowManager APIs. It then uses SplitController and a split attributes calculator to respond to changes in window or device state, including folding and tabletop posture. The walkthrough also switches between a navigation rail and bottom navigation as the available space changes.
Read the original →ArticleAndroid
Android Developers · Google
Google explains how folded, flat and tabletop postures affect the arrangement of content and controls. The hinge guidance recommends considering where text and controls sit and allowing a wider gutter in pane-based layouts. Cover-screen and orientation examples help designers adapt a focused experience without assuming that every foldable supports every posture.
Read the original →ArticleAndroid
Android Developers · Google
Google’s official guide to reading fold state with Jetpack WindowManager. It shows how to get a FoldingFeature, tell whether the device is flat or half-opened, and check whether the hinge splits the window. From there you can design for tabletop (half-open, hinge horizontal) and book (half-open, hinge vertical) postures instead of letting content fall into the crease.
Read the original →ArticleAndroid
Android Developers · Google
This guide separates visual layout checks from state-restoration tests when a foldable changes size or configuration. It explains using StateRestorationTester or Activity.recreate() to exercise restoration, and distinguishes those checks from posture-specific tests that need a suitable foldable device or emulator. It also covers UI behavior and screenshot tests for layout regressions.
Read the original →ArticleiPhone Duo
Apple Developer · Apple · 2026
Apple’s device-specific HIG explains how size classes, safe areas and reserved regions shape layouts across Duo’s inner and outer displays. It covers split and arrangement views, preserving controls and state through resizing, and the placement of vertical bars. The guidance favors small layout adjustments around the fold while keeping the app’s functionality consistent.
Read the original →ArticleiPhone Duo
Apple Developer · Apple
This Apple Tech Talk explains how SDK selection affects screen use on Duo, then walks through flexible layout, size classes and asymmetric safe areas. It shows how standard SwiftUI and UIKit navigation adapts, introduces reserved-region handling for custom interfaces, and describes Device Hub checks. The transcript also identifies the App Resizability skill as an aid for reviewing layout assumptions.
Read the original →ArticleHarmonyOS / OpenHarmony中文
Huawei HarmonyOS Developers · Huawei
Huawei’s HarmonyOS guide uses window-size changes and breakpoints to keep layouts continuous while a device folds, rotates or changes window mode. It distinguishes responsive resizing from posture-specific behavior and warns against relying only on fold-status events for layout. List examples use onScrollIndex() and scrollToIndex() to preserve the reader’s position after a fold.
Read the original →ArticleHarmonyOS / OpenHarmony中文
Huawei HarmonyOS Developers · Huawei
Huawei’s versioned HarmonyOS V14 guide covers layouts and window behavior across folded, expanded and hover states. It shows how display.on('foldStatusChange') can drive posture-specific behavior, and how FolderStack or getCurrentFoldCreaseRegion() supports crease avoidance. Responsive layout and multi-window sections explain how to use additional screen space without stretching a phone layout.
Read the original →ArticleHarmonyOS / OpenHarmony中文
Huawei HarmonyOS Developers · Huawei
Huawei’s HarmonyOS ArkUI reference documents FoldSplitContainer, a component for two- or three-region layouts across expanded, hover and folded states. It explains primary, secondary and optional extra builders, per-state layout options, and the window-width and posture conditions for hover behavior. Examples demonstrate configuring the regions while accounting for the crease.
Read the original →ArticleHarmonyOS / OpenHarmony
Huawei HarmonyOS Developers · Huawei
Huawei’s HarmonyOS guide compares FolderStack, FoldSplitContainer and custom layouts for semi-folded use. It explains how to place media and controls above or below the crease, then shows a custom approach using fold-state listeners and getCurrentFoldCreaseRegion(). The comparison helps choose between built-in layouts and explicit posture or rotation policies.
Read the original →