Foldable phones are no longer a niche category. In 2026, Samsung's Fold series, the Pixel Fold 2, and OnePlus Open collectively account for a meaningful share of flagship Android sales — and all major manufacturers have announced foldable roadmaps. If your app doesn't handle fold/unfold gracefully, you're now degrading the experience for a significant segment of premium users.
1. Handle Configuration Changes Correctly
Folding and unfolding generates configuration changes (screen size, density, aspect ratio). Your Activity must survive these without restarting. Add windowLayoutMode to your manifest, handle state preservation with ViewModel, and test that no data is lost during a fold/unfold mid-operation. Most fold-related crashes come from configuration change handling, not foldable-specific APIs.
2. Adopt Jetpack WindowManager
Jetpack WindowManager 1.3+ provides: WindowInfoTracker for fold state (FLAT, HALF_OPENED), FoldingFeature for hinge position and orientation, and WindowSizeClass for breakpoints (Compact/Medium/Expanded). Collect WindowLayoutInfo from a coroutine scope and update your layout accordingly. Don't hardcode screen size assumptions — use WindowSizeClass everywhere.
3. Table-Top Mode: The Overlooked State
Half-open (table-top) mode — phone sitting like a laptop — is a unique interaction paradigm. Content in the upper half, controls in the lower half. Video apps should auto-enable picture controls at the hinge. Maps should show the route in the upper pane and turn-by-turn in the lower. Use FoldingFeature.State.HALF_OPENED and FoldingFeature.Orientation.HORIZONTAL to detect this state.
4. Adaptive Layouts with Jetpack Compose
In Compose, use adaptive-layout-android library's ListDetailPaneScaffold and SupportingPaneScaffold. These handle the master-detail pattern automatically across compact (single pane), medium (side-by-side), and expanded (full two-pane) window sizes. Don't build your own breakpoint system — use the scaffolds and let WindowSizeClass drive the layout.
5. Test on Real Hardware and Emulator
The Android Emulator includes foldable device definitions (7.3" fold, flip). Run your test suite against these. Use the Fold State dropdown in the extended controls to simulate fold/unfold during test execution. Also test on physical hardware — emulator fold physics aren't perfect and hinge behavior varies between manufacturers.
6. Large Screen Quality Guidelines
Google's Large Screen Quality guidelines (Tier 1–3) are becoming a Play Store ranking signal. Tier 1 (basic compatibility) is the minimum. Tier 2 (responsive layout) is what most apps should target. Tier 3 (optimised for large screens with productivity features) is the differentiator. Check your app against the guidelines at developer.android.com/large-screens.