Foldable App Testing: Is Your App Ready to Unfold?

Foldable App Testing: Is Your App Ready to Unfold?
November 19 10:21 2026 Print This Article

Standard mobile testing won’t cut it once hardware starts bending, and that is where foldable app testing begins. An app holds up on a foldable when dynamic display shifts leave active sessions untouched and trigger clean layout reflow instead of sudden crashes. Without deliberate continuity testing, sudden screen resets can corrupt input fields and interrupt critical transaction flows.

Folding breaks the basic mobile rule of a fixed screen, so that difference defines foldable app testing. On Android, this triggers a configuration change that recreates the active Activity by default, and the app has to survive it.

That risk scales with the market as IDC projects foldables as virtually the only growing smartphone segment in 2026 [1], and expects Apple to take roughly 40% of the foldables market by 2027.

Foldable Form Factors and Market Adoption

Priorities for testing apps on foldable devices depend on the hardware users actually have.

Flips, Folds, and Tri-Folds

Even with the same codebase, each format can show different failure points. Clamshell phones switch between a small outer screen and a tall vertical view, and book-type models jump from phone dimensions straight into tablet territory. The multi-hinge tri-folds add intermediate screen ratios.

Interfaces built only for fixed portrait layouts can break their layout reflow when the window expands.

Foldable form factorsScreen configurations, QA risks and device examples
Form factorScreen configurationQA riskDevice examples
Book-type Narrow cover screen, large inner display Session continuity loss and multi-column reflow errors Galaxy Z Fold, iPhone Duo
Flip / Clamshell Compact external screen, tall vertical internal display Tabletop posture clipping and limited outer display actions Galaxy Z Flip, Razr series
Tri-fold Dual-hinge panel opening across two unfold stages Cascading window resize events and intermediate ratio glitches Huawei Mate XT, Galaxy Z TriFold
Wider book-type Broader aspect ratios on both displays Premature desktop breakpoints and compressed text columns Recent wider foldables

Market Realities: Foldables Grow as iPhone Duo Arrives

Counterpoint estimates cumulative foldable shipments will pass 100 million units by late 2026 [2]. These are premium devices, as IDC puts the average price of Apple’s foldable above $2,550 [1]. For mobile application testing, this makes foldables a priority rather than an edge case, because when an unhandled fold breaks an active session, the app lets down the users who paid the most for their phones. 

Apple’s iPhone Duo brings the same task to iOS. Apps built with the iOS 27 SDK and later resize dynamically when the device folds and unfolds [3]. Both platforms now expect apps to adapt to window sizes that change mid-session [3][4].

What Foldable App Testing Needs to Cover

On a standard smartphone, an app launches into a fixed viewport. A foldable changes screen dimensions during active use, and that requires QA teams to cover four core behaviors:

  • Window bounds. The operating system recalculates screen dimensions in use. Navigation panels and split views must adapt to dynamic window size classes when the device shifts. 
  • Lifecycle and state. On Android, folding can trigger a configuration change that, by default, destroys and recreates the foreground Activity. Without deliberate verification of app continuity, this reload can wipe unsaved inputs and cancel background operations tied to the screen.
  • Hinge area. On some devices, the hinge physically hides part of the display. On most current foldables, the screen stays continuous, but the bend is still hard to see and tap. In tabletop posture, action buttons and modal sheets can end up over the bend.
  • Camera preview. The display aspect ratio changes, and the camera sensor keeps its own. If the viewfinder does not recalculate the preview frame, images look stretched and barcode scans fail.

Testing requires evaluating these transitions in motion. Flexing the hardware during active tasks works better than simply inspecting static views.

Where Real Defects and Technical Causes Appear

Layout defects become more frequent once software runs on a screen that changes size. A 2026 study by Zhang et al. [5] tested 50 real Android applications in two settings: conventional full-screen and split-screen/foldable. Compared with full-screen, the number of detected cases of text overlap rose by 137%, widget occlusion by 196%, and text truncation by 184%. The researchers’ detection method flagged at least one GUI display defect in 40 of the 50 applications (80%) in split-screen/foldable mode, compared with 32 in full-screen.

Layout is only part of the picture. Another class of failures appears when the window size changes while the app is running and the app’s lifecycle must handle the change. The table below lists public defects reported in production apps and in SDKs that other apps build on. An SDK defect spreads further, since every app that uses it inherits the failure.

Foldable bugs in real appsWhat happens, the reported cause and the result
AppWhat happensReported causeResult
Brave (Android) Open tabs close on fold or unfold when “Close tabs on exit” is enabled Activity recreation is treated as an app exit, which triggers the “Close tabs on exit” setting User may lose the browsing session and unsaved data
Bluesky (Android) Open post or comments disappear after unfolding, app returns to the feed State is not restored after a configuration change User loses their place in a thread
VisionCamera SDK (iOS) Camera preview turns sideways after unfolding and rotating Preview does not follow window rotation Photo, video, and scanning flows break on iPhone Duo
Braintree SDK (Android) 3D Secure check fails with HTTP 422 A used transaction nonce is sent again after Activity recreation Payment is rejected, and the merchant can lose the sale

Android 16, Android 17, and iOS Platform Changes

Android has been tightening the rules for two releases now. Since Android 16, the system ignores orientation and aspect ratio locks by default on large screens for apps that target API level 36, meaning anything with a smallest width of 600 dp or more [6]. Google Play has required API 36 for new apps and updates since August 31, 2026, so the new default now applies to any phone app that ships an update [7]. Games are the exception, and users can still switch an app back in settings [6]. Other apps can still opt out temporarily on API 36 [6], but Android 17 removes that option for apps targeting API 37 [8]. So the letterbox is on its way out, and a layout built for a vertical phone has to hold up at any width.

On iPhone Duo, what matters is the SDK the app was built with, not the iOS version on the phone. With the iOS 26 SDK or earlier, the app sits in a centered window with empty space around it. With the iOS 27 SDK, it fills most of the inner display but stays clear of the status bar on the right. With 27.1, it goes edge to edge, and toolbars and tab bars move into a vertical layout under the status bar [3]. Apple asks developers not to read the main screen bounds or hard-code phone dimensions. An app that still does either may look fine today and break the moment it’s rebuilt on a newer SDK.

Foldable App Testing Checklist. What Areas You Need to Verify?

Running each area on at least one foldable and one tablet works well here. Plus, consider both device states. The check is passed if the unit still works after transition.

Foldable testing checklist

What to check?

Screen Adaptation Across Size Classes

  • Layout fits compact, medium, and expanded windows without clipped or overlapping elements.
  • Navigation switches to the right pattern for each size.
  • The content stays readable in tabletop and book postures.
  • A flip model’s cover screen shows the supported screens or hands off to the main display.

Testing type: Compatibility testing

State Restoration

  • Text typed into forms is still there after folding and unfolding.
  • Scroll position and the selected tab stay the same.
  • Active sessions (login, video, download, checkout) do not need a restart.
  • The app does not return to the home screen or the feed after the change.

Testing type: Functional testing

Hinge Area and Reserved Regions

  • No buttons, input fields, or key text sit on the fold line.
  • Modal sheets and dialogs open clear of the hinge area.
  • Content stays out of system bars, cutouts, and gesture zones.
  • Insets update after every posture change.

Testing type: GUI testing

Resizing, Rotation, and Multi-Window Mode

  • The app resizes correctly in split-screen and while the divider is dragged.
  • Picture-in-Picture works without losing playback or position.
  • Input focus stays on the active field after a rotation or resize.
  • Rotation works in both device states with no layout reset.

Testing type: Compatibility testing

Virtual Keyboards and Text Input

  • The focused field stays visible above the keyboard in every window size.
  • Cursor position and selection survive a fold with the keyboard open.
  • Split or floating keyboards do not cover the submit button.
  • Autofill and password managers keep working after a size change.

Testing type: UX / Usability testing

Camera Viewfinder and Media Aspect Ratios

  • The preview fills the frame without stretching or distortion.
  • QR and barcode scans work in both states and in each posture.
  • Captured photos and videos keep the correct orientation and ratio.
  • Images and video are not cropped unexpectedly.

Testing type: Functional testing

Payments and Authentication Flows

  • Payment and 3D Secure checks finish when the device is folded mid-flow.
  • The app does not resend a used transaction token after the screen is recreated.
  • OAuth sign-in and biometric prompts return to the correct screen.
  • Two-factor setup, including the QR scan, works after a state change.

Testing type: Functional testing and Security testing

Transition Stability and Performance

  • No crashes or ANRs across 20 fold and unfold cycles in a row.
  • Memory use returns to its starting level after the cycles.
  • No flicker, white screen, or frozen frame during the transition.
  • The transition finishes in acceptable time with media or long lists open.

Testing type: Performance testing

Accessibility Across Both Displays

  • Large font sizes and display zoom do not truncate or overlap text in either state.
  • Touch targets stay at least 48 dp on Android and 44 pt on iOS after resizing.
  • TalkBack and VoiceOver keep a logical focus order and read the new layout after the change.
  • Contrast and focus indicators hold in both layouts.

Testing type: Accessibility testing

How to Build a Foldable App Testing Strategy

Building a device matrix for testing apps on foldable devices starts with your real audience. Check your app store analytics to see which foldable models your users already own and test those phones first. Once you cover existing traffic, expand the matrix to address specific form-factor risks:

  • A book-type phone. Pick the most popular brand among your users. Test both open and closed screens, including tabletop mode.
  • A clamshell flip phone. Check how the app behaves on the full display and on the outer cover screen.
  • A standard tablet. Use it as your baseline to verify wide screens and multi-column layouts.
  • A tri-fold or iPhone Duo. Add these to a second test phase once your user numbers justify the hardware cost.

Prioritize test scenarios by business risk. Checkouts and account logins come first, followed by multi-step data entry. Next, test camera tools, leaving passive browsing for last.

Emulators and Simulators vs. Real Hardware Labs In Foldable App Testing

Emulators speed up regression cycles by validating layout bounds and programmatic state resets in automated builds. However, simulated displays cannot expose physical hinge dead zones or real sensor timings. Practical real device testing for foldables captures what software simulation misses. Use the matrix below to divide test coverage between virtual runs and physical lab hardware.

Emulator vs real deviceWhat each option covers in foldable testing
CheckEmulator / SimulatorReal device
Layout across window sizes and size classes Sufficient Confirm on one device
State restoration after a configuration change Sufficient for a first pass Required before release
Tabletop and book postures Basic cases through virtual posture controls Required: real hinge angle and sensors
Hinge area and cutout geometry Approximate Required
Camera preview and QR scans Limited Required
Gestures across the fold, drag in multi-window Limited Required
Memory and stability over repeated folds Unreliable Required

Purchasing every foldable flagship drains budgets quickly. When release validation requires testing across multiple brands, partnering with an external QA lab can cover the full device matrix. QATestLab lets you test on real devices only when you need them. Take a look at our Mobile Device Lab presentation to see which devices are available and pick the right mix for your next launch.

What to Test on Android and on iOS

Testing foldables requires distinct verification passes for each operating system because Android and iOS handle dynamic displays differently.

On Android

  • Window size classes and hinge placement. Check how the interface reflows when the screen expands or folds, using dimensions from Jetpack WindowManager. Use FoldingFeature to see where the fold is and whether it actually hides content on the device under test.
  • State preservation during Activity recreation. Test that entered text, scroll positions, and payment steps remain intact during every fold, since Activity recreation clears anything the app does not save.
  • Display policies in Android 16 and 17. Raise the target API to 36 or 37 and check that a portrait-first layout holds up on a large screen without letterboxing.

On iOS

  • Dynamic bounds over fixed dimensions. Check that views take their size from the window, not from hardcoded iPhone values, and update it on every fold. Apps that read the main screen bounds or treat regular width as “iPad” can end up with clipped buttons and broken grids.
  • State continuity across scenes. Ensure that active user sessions persist through multitasking splits and window resizing. Unsaved form entries and media playback must survive transitions between different window modes.
  • iPhone Duo and the SDK. Layout on iPhone Duo depends on the SDK the app is built with. On the iOS 27.1 SDK, toolbars turn vertical, and controls must stay clear of the status bar and camera. Test in the iPhone Duo simulator in Xcode 27.1.

Manual vs. Automated Testing: Where Each Fits

The split follows repeatability. Send to automation any scenario that runs on every build and needs no human judgment. Anything that depends on the hinge, touch, camera, or the feel of the screen usually stays manual.

Manual vs automatedWhat to test by hand and what to automate

Manual

  • Posture changes on a real hinge
  • Gestures across the fold
  • Camera and QR scans
  • Keyboard and one-handed use
  • Visual review of layouts

Automated

  • Repeated fold, unfold, and rotate cycles
  • State restoration on scripted flows
  • Window resizing on emulators in CI
  • Payment flow checks through the API
  • Screenshot comparison across window sizes

Acceptance Criteria and Blocker Defects Before Release

Block the release when any of these appear on a supported device:

  • A crash or ANR during fold, unfold, or rotation.
  • Lost user input or session data after a posture or window change.
  • A failed or repeated payment or authentication after a configuration change.
  • A primary action is unreachable: a button under the hinge, behind the keyboard, or outside the visible window.
  • A broken camera preview or QR scan.

Cosmetic layout defects that do not affect the task, such as uneven spacing in an intermediate tri-fold state, can ship with a ticket and a fix date. Agree on this list with product and development before testing starts, so the release decision does not turn into a debate at the end.

Regression Strategy and Automation

Keep a fixed foldable pack and run it on a schedule:

  • On every build: a smoke pack on the three most important flows, on an emulator in CI.
  • Before every release: all nine checklist areas on the real devices from the matrix.
  • After each OS or SDK update: Android 16 and 17 and iOS 27 changed window behavior, so each new version needs a rerun.
  • After each field defect: every confirmed bug becomes a permanent test case.

Crash reports and analytics filtered by foldable models show what testing missed. Feed those findings back into the matrix and the pack.

Conclusion

Adapting to foldables is turning from a nice-to-have into a requirement, and foldable app testing has to keep up. Since Google Play started requiring API level 36, a phone app that ships an update loses its portrait lock on large screens by default, and the temporary opt-out ends with API 37. On iPhone Duo, an app rebuilt with the iOS 27 SDK loses its compatibility frame and has to resize every time the device folds. Apps that aren’t ready fail in familiar ways: forms lose their input, checkouts break halfway, buttons slide under the status bar, and stretched camera previews stop reading QR codes. Emulators catch many of these problems early and cheaply, but the hinge, the crease, and the camera still need real hardware.

This is where teams can get stuck. A matrix that covers book-type, flip, and tri-fold models from several brands quickly outgrows a single team’s budget, and it needs a rerun after every Android release and every new iOS SDK. The devices also age fast, so last year’s flagship may no longer match what your users carry. QATestLab offers access to a dedicated pool of real devices, so you can test on the models that matter for your audience when a release actually needs them. Contact us to choose the right models and secure your next release.

FAQ

Why do apps lose user data when a foldable is folded or unfolded?

On Android, folding or unfolding triggers a configuration change, and the system destroys the active screen and rebuilds it. Without state preservation, typed text, scroll positions, and running tasks can disappear after the rebuild. Fixing this requires proper lifecycle handling, and foldable app testing confirms that active sessions stay intact across transitions.

What kinds of defects appear most often on foldables?

The most common defects on foldables are visual layout issues, but session resets carry a higher business risk. In a study of 50 Android applications, the researchers’ detection method found GUI display defects in 40 of them (80%) in split-screen and foldable modes. Text overlap, truncation, and widget occlusion appeared far more often there than in full-screen. In production, folding can restart the active screen, erasing form data and aborting checkout flows.

Which user flows deserve the most attention on a foldable?

The flows that deserve the most attention on a foldable are the ones with the highest cost of failure. Checkout and account login come first, since a broken payment or sign-in is lost revenue. Multi-step forms follow, then camera and scanning tools, with passive browsing last.

How often should foldable regression tests run?

Foldable regression tests usually run at several stages, not just once before launch. With every new build, a quick automated check covers the three most important user flows. Before a release, the team goes through the full nine-area checklist on real foldable phones. After a new Android version or iOS SDK comes out, the team runs the tests again. When users report a new fold-related bug, it becomes a regular test case so the same problem doesn’t return.

Which foldable tests can be automated?

Most repeatable foldable checks can be automated, especially those that don’t require a person to judge how the app looks or feels. These include repeated fold-and-unfold cycles, state restoration in scripted user flows, and window resizing on emulators. Screenshot comparison across different window sizes also works well in automation. Physical interactions are a different story, so hinge angles, gestures across the fold line, and camera scanning are still best checked by hand on real devices.

References

[1] IDC, “Smartphone Shipments Set for Record 16.7% Drop in 2026, as the Memory Crisis Hits Full Force.” https://www.idc.com/resource-center/blog/smartphone-shipments-set-for-record-16-7-drop-in-2026-as-the-memory-crisis-hits-full-force/
[2] Counterpoint Research, “Global Foldable Shipments to Hit 100-million Cumulative Milestone by End of 2026.” https://counterpointresearch.com/en/insights/global-foldable-shipments-to-hit-100-million-cumulative-milestone-by-end-of-2026
[3] Apple Developer, “Three Steps to Make Your App Shine on iPhone Duo.” https://developer.apple.com/iphone-duo/prepare
[4] Android Developers, “Foldables | App Quality.” https://developer.android.com/docs/quality-guidelines/adaptive-app-quality/experiences/foldables
[5] X. Zhang et al., arXiv, “Proactive Detection of GUI Defects in Multi-Window Scenarios via Multimodal Reasoning.” https://arxiv.org/html/2604.19081v1
[6] Android Developers, “Behavior Changes: Apps Targeting Android 16 or Higher.” https://developer.android.com/about/versions/16/behavior-changes-16#ignore-orientation
[7] Google Play Console Help, “Target API Level Requirements for Google Play Apps.” https://support.google.com/googleplay/android-developer/answer/11926878
[8] Android Developers, “Restrictions on Orientation and Resizability Are Ignored.” https://developer.android.com/about/versions/17/changes/ff-restrictions-ignored
[9] GitHub, react-native-vision-camera, “[iPhone Duo] Cameras Are Rotated 90° Clockwise When Using the Camera on the Inner Display” (Issue #4236). https://github.com/margelo/react-native-vision-camera/issues/4236

Related Posts:

About Article Author

view more articles
Yuliia Polonska
Yuliia Polonska

View More Articles