The foldable developer’s field guide

Build forevery fold.

Find the patterns, tools and real-world lessons to make your app feel at home on every screen.

posture: folded → compact · one columnposture: unfolded → expanded · two-paneposture: half-open → book · split at hinge

01 / Find a starting point

What are you working on?

Explore the Kit ↗

02 / From reading to building

A little less starting from scratch.

Latest guides

View all ↗
AndroidAndroid Developers

Adaptive app quality guidelines

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 ↗
AndroidReact Native Docs

Dimensions

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 ↗
AndroidFlutter API

displayFeatures property

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 ↗

Open-source toolkit

17 published
Explore tools ↗

03 / Across the ecosystem

Across foldable ecosystems.

Browse resources and see how much posture evidence the linked sources provide.

Explore Apps ↗
Source coverage19 resources

iPhone Duo

—No complete posture reports
0 complete passing reports0 with reported issues19 without complete posture evidence0 of 19 documented in all three postures
Source coverage15 resources

Android

—No complete posture reports
0 complete passing reports0 with reported issues8 without complete posture evidence0 of 8 documented in all three postures
Source coverage11 resources

HarmonyOS / OpenHarmony

—No complete posture reports
0 complete passing reports0 with reported issues3 without complete posture evidence0 of 3 documented in all three postures

04 / From the people using it

Start with the friction.

Small layout decisions change how an app feels. Follow the feedback, then find a technique to address it.

Explore User Voice ↗
complaint

A Samsung foldable user reports CDisplayEx leaving an unused strip in split view while normal folded and unfolded views use the space correctly. The author then edits the post to say the system’s multi-window full-screen setting resolved the issue.

Reddit · r/GalaxyFold ↗
complaint

A Fold7 user has difficulty restoring a stacked inner-screen layout for videos after an update. They clarify that a floating window is not the desired result. A reply explains the divider menu and app pairs, and the author thanks them; the thread does not establish that stacked layouts were removed.

Reddit · r/GalaxyFold ↗
About this index Sources, sample data & evidence coverage

Homepage totals include published, non-demo content. Tools are counted once per GitHub repository. Apps tracked counts source-linked app profiles per platform, including entries with no documented posture results. Owner insights count sourced feedback entries, not individual people.

A complete source report documents folded, unfolded and half-open. A percentage is shown only when complete reports exist; a dash means no complete source evidence is available. FoldKit summarizes sources and does not run the apps. Placeholder records are excluded from the directories.