AppReviewX Log in

Test your app in split-screen and multi-window

A short list to catch state loss and layout issues when the window size changes.

In this guide

In split-screen, your app may get half the screen, or a small floating window, and the user can drag the divider at any time. Each resize can recreate your screen. If state is not kept, the user loses input. If the layout assumes a full screen, it breaks. This list is short on purpose.

Start split-screen

Steps differ by device and manufacturer. Typically: open the recent apps view, tap the app icon or its menu at the top of the app card, and choose Split screen (or similar), then pick a second app. On some devices you can also drag a window into a floating one. Keep a second app open that is easy to recognize, such as a clock or notes app.

Checklist

  1. Launch in a half-size window. Open your app directly in split-screen. Why: a screen may never have been drawn at that size. Check: open every main screen; look for cut-off content.
  2. Drag the divider. Resize slowly and quickly, to both extremes. Check: layout adapts without overlap, and nothing stays frozen at the old size.
  3. Input survives a resize. Type into a field, then resize. Why: resizing can recreate the screen. Check: the text, cursor and scroll position remain.
  4. Position survives. Scroll a long list, open a detail screen, then resize. Check: you remain on the same screen at the same place.
  5. Media and ongoing work. Video, audio, timers, uploads. Check: they continue or pause in a way the user expects; no crash or duplicate playback.
  6. Dialogs and bottom sheets. Check: open one, resize, and make sure it stays readable and dismissible.
  7. Keyboard. The keyboard takes more of a small window. Check: the field being edited stays visible and the Done button is reachable.
  8. Small width and height. The narrowest window behaves like a tiny device. Check: the same points as in screen size testing.
  9. Focus changes. Tap the other app, then back. Check: your app resumes correctly and does not reset.
  10. Two apps at once. If your app uses the camera, microphone or audio focus, run it next to an app that does too. Check: no crash, a clear message if the resource is busy.
  11. Rotation in split-screen. Check: see rotation and configuration changes.
  12. Restart from split-screen. Close and reopen. Check: the app starts normally in full screen.

Fixing what you find

Most failures trace to two causes: layouts that read the screen size once instead of reacting to the window, and state kept only in memory. Save the state the user would miss, such as input, scroll position and selection, and restore it. The same state work helps with process death.

Limits

Some apps or screens deliberately do not support multi-window, for example a game or a camera view. That is a design choice; check that your app then behaves sensibly rather than breaking. Behavior also varies by manufacturer, so note the device model with each finding.

Overview: Android app testing. Related: gesture navigation.

Start free on AppReviewX and ask testers to try your app in split-screen on their own devices.