Kit

The best foldable adaptation know-how from around the web. Each entry is a short summary in our words with a link to the original, so the credit stays with the author.

Skills

Repos that do the adapting for you: agent skills, libraries and samples on GitHub.

LibraryAndroid

Android Jetpack

androidx/androidx · Android Open Source Project · ★ 6.1K

The AndroidX repository contains the Compose Material 3 Adaptive libraries used to arrange content across changing window sizes on foldables. Its list-detail scaffold supports one, two or three panes, with optional pane expansion, while Navigation 3 integration maps navigation entries into those panes. This entry concerns the compose/material3/adaptive modules within the wider Jetpack repository.

  • #compose
  • #adaptive-layout
  • #two-pane
  • #hinge-avoidance
View the repo →
Agent skilliPhone Duo

iPhone Duo Playbook

aivars/iphone-duo-playbook · Aivars Meijers · ★ 6

This community playbook combines a phased migration checklist with fold-aware SwiftUI patterns, a code-audit helper and a packaged agent skill. It distinguishes Apple guidance from the author’s field observations and covers state continuity, accessibility and store-release artifacts. Its audit results are review signals, not compatibility verdicts.

  • #adaptive-layout
  • #continuity
  • #testing
  • #swiftui
  • #uikit
View the repo →
Agent skilliPhone Duo

iPhone Duo design toolkit

Belweave/iphone-duo-design · Belweave · ★ 8

This community design toolkit combines a Duo migration skill with SwiftUI/UIKit templates, a heuristic layout scanner and screenshot-overlay helpers. Its references cover bars, reserved regions, split arrangements and review checklists. A source ledger separates Apple guidance from the maintainer’s own layout practice and records unresolved claims.

  • #design
  • #adaptive-layout
  • #hinge-avoidance
  • #swiftui
  • #uikit
View the repo →
Agent skilliPhone Duo

iPhone Duo: audit, update, validate

mattbirchler/iphone-duo-skill · mattbirchler · ★ 7

This community audit-and-migration workflow organizes iPhone Duo work around resizing, system bars, pane arrangements, reserved regions and camera direction. It pairs a source scanner with topic-specific references and verification instructions. Apple reference pages are downloaded separately by a helper, so the README includes a documentation setup step.

  • #adaptive-layout
  • #hinge-avoidance
  • #continuity
  • #swiftui
  • #uikit
View the repo →
SampleHarmonyOS / OpenHarmony中文

OpenHarmony application samples

openharmony/applications_app_samples · OpenHarmony · ★ 8

OpenHarmony’s sample collection includes a FoldableAdaptation project that switches ArkUI Navigation between stack and split modes. The example combines windowSizeChange breakpoints with route-stack changes, including separate handling for full-screen detail pages. This entry concerns the code/UI/FoldableAdaptation example within the much broader application-samples repository.

  • #adaptive-layout
  • #two-pane
  • #arkui
View the repo →
SampleAndroid

Adaptive apps samples

android/adaptive-apps-samples · Google · ★ 79

Google’s Android sample projects include list-detail, feed and supporting-pane layouts in Compose and Views for phones, tablets and foldables. The repository also contains adaptive media and navigation examples for comparing implementation patterns as screen space changes. Start with the CanonicalLayouts directory for side-by-side content.

  • #adaptive-layout
  • #two-pane
  • #compose
  • #android-views
  • #media
View the repo →
Agent skillAndroid

Android skills

android/skills · Google · ★ 11K

Google’s Android agent-skill collection includes a dedicated adaptive UI workflow for Compose apps. The adaptive skill covers multi-pane layouts, preserving UI and media state through folding or resizing, and tabletop layouts for foldable devices. It assumes Compose screens and Navigation 3, so those prerequisites should be checked before applying the instructions.

  • #adaptive-layout
  • #two-pane
  • #continuity
  • #postures
  • #compose
View the repo →
Agent skilliPhone Duo

iphone-duo — an agent skill for building iPhone Duo apps

Auspexlabs/iphone-duo-skill · Auspexlabs · ★ 1

This community-maintained SwiftUI skill pairs fixed and joined pane arrangements with guidance on vertical toolbars, state continuity and simulator capture. The repository includes sample apps and SDK-inspection helpers for investigating fold transitions. Its simulator observations and layout choices should be checked against the app’s own toolchain and requirements.

  • #swiftui
  • #two-pane
  • #continuity
  • #postures
  • #testing
View the repo →
Agent skilliPhone Duo

iPhone Duo Skill

Bunn/iphone-duo-skill · Bunn · ★ 19

This community SwiftUI/UIKit skill combines an iPhone Duo developer guide with an implementation workflow and small API-declaration probes. Its references cover fold and camera regions, vertical bars, scene transitions and state continuity. A companion guide explains how to combine Duo-specific work with Xcode’s exported layout and SwiftUI skills.

  • #swiftui
  • #uikit
  • #adaptive-layout
  • #continuity
  • #media
View the repo →
Agent skilliPhone Duo

iPhone Duo Skill

d-date/iphone-duo-skill · d-date · ★ 46

This English community adaptation guide is organized into layout, bars, scenes, cameras and a migration checklist. It explains size-class-driven layout, asymmetric safe areas and preserving view identity as the device folds. Its reference notes include the author’s simulator observations about reserved regions and Split View, with a changelog recording corrected earlier guidance.

  • #swiftui
  • #uikit
  • #adaptive-layout
  • #hinge-avoidance
  • #continuity
View the repo →
Agent skilliPhone Duo

iPhone Duo Agent Skill

eisenjimmy/iphone-duo-skill · eisenjimmy · ★ 15

This community skill organizes iPhone Duo work into universal adaptive layout, fold-aware presentation and optional hardware capabilities. It supplies an audit workflow, an API manifest with evidence status, and references for bars, reserved regions, scenes and testing. The guidance emphasizes preserving navigation and editing state and reporting SDK or verification limits explicitly.

  • #swiftui
  • #uikit
  • #adaptive-layout
  • #hinge-avoidance
  • #continuity
View the repo →
Agent skilliPhone Duo

iPhone Duo Skills

hechen/iphone-duo-skills · hechen · ★ 7

This community collection provides focused agent workflows for iPhone Duo readiness, design, layouts, bars, scenes, camera behavior and testing. Its layout skill separates navigation from pane arrangement and preserves model identity through folding; its testing skill records device or simulator evidence separately from resize-only proxy checks. Duo-specific instructions assume a suitable iOS 27.1 SDK.

  • #adaptive-layout
  • #hinge-avoidance
  • #continuity
  • #testing
  • #swiftui
View the repo →
Agent skilliPhone Duo

Apple HIG Skill

justinwetch/HIGAgentSkills · justinwetch · ★ 834

This community Apple HIG skill includes a /duo workflow for assessing an existing SwiftUI or UIKit app, matching its screens to the bundled guidance, implementing native changes and recording verification. Its Duo checklist addresses layout, state continuity and fold-related controls. The repository distinguishes code review, simulator observations and on-device verification.

  • #design
  • #adaptive-layout
  • #continuity
  • #swiftui
  • #uikit
View the repo →
Agent skilliPhone Duo

iPhone Duo Skills

mirzaaghazadeh/iphone-duo-skills · mirzaaghazadeh · ★ 322

This community skill collection organizes iPhone Duo adaptation by task and application stack, including native iOS, Flutter, React Native and Capacitor. The adaptive-layout skill explains reserved-region handling, while the Flutter skill separates constraint-based layout changes from native bridge work. Source notes record API corrections and unresolved documentation differences that users should recheck against their SDK.

  • #adaptive-layout
  • #hinge-avoidance
  • #swiftui
  • #flutter
  • #react-native
View the repo →
Agent skilliPhone Duo

iphone-duo-fit

Pursuitli/iphone-duo-skills · Pursuitli · ★ 4

A community agent workflow for fitting existing SwiftUI and web/Capacitor apps to iPhone Duo poses, with particular attention to custom controls and side bars. It includes a screen-by-pose audit, native and web recipes, and screenshot-measurement scripts. The proposed dimensions and device checks come from the author’s simulator work and should be validated for the app and runtime being adapted.

  • #adaptive-layout
  • #postures
  • #continuity
  • #testing
  • #swiftui
View the repo →
Agent skilliPhone Duo

iPhone Duo Skills

RV784/iphone-duo-skills · RV784 · ★ 3

This community toolkit provides an iPhone Duo adaptation checklist plus audits for Swift, Objective-C and Interface Builder layouts. It covers resizing assumptions, asymmetric safe areas and fold-aware interface changes, with a companion workflow for researching Apple documentation. Audit findings are candidates for review and still need checking against the target SDK and runtime.

  • #adaptive-layout
  • #testing
  • #hinge-avoidance
  • #swiftui
  • #uikit
View the repo →
Agent skilliPhone Duo

iPhone Duo Migration Skill

TanShilongMario/iPhoneDuo · TanShilongMario · ★ 1

This community migration skill covers SwiftUI and UIKit layout adaptation, fold-region avoidance, system toolbars and keyboard-safe editing. Its test matrix includes folding with uncommitted input, preserving selection and focus, multitasking, and ordinary iPhone regression. It also supplies a heuristic audit and reporting templates; those aids do not certify device compatibility.

  • #swiftui
  • #uikit
  • #input
  • #continuity
  • #testing
View the repo →

Articles

Write-ups, docs and talks on how other developers solved it.

ArticleAndroid

Adaptive app quality guidelines

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.

  • #testing
  • #design
  • #input
  • #postures
  • #multi-window
Read the original →
ArticleAndroid

Dimensions

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.

  • #react-native
  • #adaptive-layout
Read the original →
ArticleAndroid

displayFeatures property

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.

  • #flutter
  • #fold-state
  • #postures
  • #hinge-avoidance
Read the original →
ArticleAndroid

DisplayFeatureSubScreen class

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.

  • #flutter
  • #hinge-avoidance
  • #postures
  • #adaptive-layout
Read the original →
ArticleAndroid

Foldable devices and cameras

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.

  • #media
  • #fold-state
  • #continuity
Read the original →
ArticleAndroid

Foldables

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.

  • #testing
  • #postures
  • #multi-window
  • #media
Read the original →
ArticleAndroid

List state management

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.

  • #continuity
  • #input
  • #compose
Read the original →
ArticleAndroid

Support multi-window mode

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.

  • #multi-window
  • #continuity
  • #media
  • #android-views
Read the original →
ArticleiPhone Duo

Build a great camera experience for iPhone 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.

  • #media
  • #fold-state
  • #continuity
  • #uikit
Read the original →
ArticleiPhone Duo

Leverage multiple displays and scenes on iPhone 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.

  • #multi-window
  • #fold-state
  • #media
  • #swiftui
  • #uikit
Read the original →
ArticleiPhone Duo

Raise the bar with iPhone 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.

  • #design
  • #adaptive-layout
  • #input
  • #swiftui
  • #uikit
Read the original →
ArticleiPhone Duo

Strike a pose with adaptive layouts on iPhone 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.

  • #adaptive-layout
  • #hinge-avoidance
  • #two-pane
  • #swiftui
  • #uikit
Read the original →
ArticleHarmonyOS / OpenHarmony中文

Adapting Camera Changes in Different Fold States (ArkTS)

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.

  • #fold-state
  • #continuity
  • #media
  • #arkui
Read the original →
ArticleHarmonyOS / OpenHarmony中文

FolderStack

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.

  • #postures
  • #hinge-avoidance
  • #arkui
Read the original →
ArticleHarmonyOS / OpenHarmony中文

module.json5 configuration file

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.

  • #adaptive-layout
  • #arkui
Read the original →
ArticleHarmonyOS / OpenHarmony中文

@ohos.display (Screen Properties)

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.

  • #fold-state
  • #postures
  • #hinge-avoidance
  • #arkui
Read the original →
ArticleHarmonyOS / OpenHarmony中文

Rules overview

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.

  • #testing
  • #continuity
  • #adaptive-layout
  • #design
Read the original →
ArticleHarmonyOS / OpenHarmony中文

Using the toolbar

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.

  • #testing
  • #postures
  • #fold-state
  • #hinge-avoidance
Read the original →
ArticleAndroid

Build a list-detail layout with activity embedding and Material Design

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.

  • #two-pane
  • #adaptive-layout
  • #postures
  • #android-views
Read the original →
ArticleAndroid

Foldable Postures and orientation

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.

  • #design
  • #postures
  • #hinge-avoidance
  • #two-pane
Read the original →
ArticleAndroid

Make your app fold aware

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.

  • #jetpack-windowmanager
  • #postures
  • #compose
Read the original →
ArticleAndroid

Test different screen and window sizes

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.

  • #testing
  • #continuity
  • #adaptive-layout
  • #compose
Read the original →
ArticleiPhone Duo

Designing for iPhone 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.

  • #design
  • #adaptive-layout
  • #hinge-avoidance
  • #two-pane
  • #continuity
Read the original →
ArticleiPhone Duo

Prepare your app for iPhone 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.

  • #adaptive-layout
  • #hinge-avoidance
  • #testing
  • #swiftui
  • #uikit
Read the original →
ArticleHarmonyOS / OpenHarmony中文

Adapting to Screen Differences Across Devices

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.

  • #continuity
  • #adaptive-layout
  • #multi-window
  • #arkui
Read the original →
ArticleHarmonyOS / OpenHarmony中文

Foldable development practices

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.

  • #adaptive-layout
  • #fold-state
  • #hinge-avoidance
  • #multi-window
  • #arkui
Read the original →
ArticleHarmonyOS / OpenHarmony中文

FoldSplitContainer

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.

  • #two-pane
  • #postures
  • #hinge-avoidance
  • #arkui
Read the original →
ArticleHarmonyOS / OpenHarmony

Semi-Folded State of Foldable Screens

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.

  • #postures
  • #hinge-avoidance
  • #media
  • #arkui
Read the original →