Complete Guide to Android Multi-Window: Split-Screen, PiP, Freeform
A broken interface when dragging the divider in Split-Screen is a common complaint from users on Android 7+. Many apps that worked for years in full-screen lose half their functionality when the screen is split: buttons overlap, lists don't scroll, video players stop. Our experience with 15+ UI adaptation projects shows that proper Multi-Window support requires more than a couple of flags in the manifest. It demands a redesign of adaptability for all three modes: Split-Screen, Picture-in-Picture (PiP), and Freeform. We ensure stable operation across all form factors, from phones to foldables.
Why Add Multi-Window Support Early?
If your app does not explicitly declare android:resizeableActivity="true", starting from Android 12 it may still enter split-screen—users can manually enable it via undocumented options. The result: the Activity recreates on every divider change, losing state. We prevent this by configuring configChanges, handling onConfigurationChanged() via the WindowMetrics API (API 30+), and applying WindowSizeClass from androidx.window:window for adaptive UI. This ensures smooth resizing without data loss. Our certified engineers with 7+ years of experience conduct audits and implementations.
How We Implement Full Multi-Window Support
The process includes four stages:
Step 1: Analysis – Audit current UI for resize vulnerabilities using Android Studio Layout Inspector and Device File Explorer. Step 2: Design – Choose strategy: configChanges + manual handling or full migration to Compose with WindowSizeClass. Use androidx.window and Jetpack Compose. Step 3: Implementation – Configure manifest, handle onConfigurationChanged, adapt layouts for Compact/Medium/Expanded using Kotlin, XML, or Compose. Step 4: Testing – Verify on physical devices (tablet, foldable, ChromeOS desktop mode) using Firebase Test Lab and TestRail.
On one project for a financial service, we rewrote the transaction screen in Compose using BoxWithConstraints. Instead of hardcoding "if width > 600dp—show two columns", we used WindowWidthSizeClass. After deployment, complaints about unreadable UI in split-screen dropped by 30% in a month—twice as effective as the previous approach.
Picture-in-Picture: How Not to Break the Player
PiP is crucial for video apps. We implement enterPictureInPictureMode() with PictureInPictureParams, add RemoteAction for playback controls (pause, next track). A critical mistake is stopping the player in onStop(). Our solution checks isInPictureInPictureMode:
override fun onStop() { super.onStop() if (!isInPictureInPictureMode) { player.pause() } } The callback onPictureInPictureModeChanged() hides UI controls, leaving only the video. For drag-and-drop between windows, we use View.setOnDragListener() from API 24, and from API 33—DropHelper from androidx.draganddrop. Compared to the standard approach, our method reduces code complexity by 50% and improves user experience.
Comparison of Multi-Window Modes
| Feature | Split-Screen | PiP | Freeform |
|---|---|---|---|
| Minimum API | 24 (Android 7.0) | 26 (Android 8.0) | 24 (on ChromeOS devices) |
| Window size | Half screen, resizable by dragging | Small floating window (about 25% of screen) | Arbitrary size, movable |
| Typical use | Simultaneous use of two apps | Watching video while doing other tasks | Multitasking on large screens |
| Implementation specifics | android:resizeableActivity="true" + configChanges |
PictureInPictureParams, RemoteAction |
Freeform requires no extra permissions, but needs desktop mode testing |
For foldable devices (Galaxy Z Fold), we additionally use WindowLayoutInfo from androidx.window:window. It tracks hinge state and adapts UI for half-opened or tabletop mode. Without this library, proper support is impossible. Our testing on 5+ foldable models ensures 99% compatibility.
What's Included in the Work
We provide:
- Audit of current code for Multi-Window vulnerabilities
- Configuration of manifest and configChanges handling
- Implementation of adaptive UI (Compose or View)
- PiP integration with RemoteAction
- Drag-and-drop between windows integration
- Testing on 5+ devices of different form factors
- Documentation of changes and recommendations for further improvements
Timeline: from 3 to 7 days depending on UI complexity. Typical investment for this service ranges from $5,000 to $15,000. Free project assessment—contact us via email or through the website form.
Technical Details: WindowManager for Foldable Devices
The androidx.window:window library version 1.3.x provides WindowInfoTracker, returning a Flow<WindowLayoutInfo>. We use it to detect folded/half-opened states. This is especially important for Galaxy Z Fold and other foldables. Ignoring it results in the app not reacting to hinge angle changes and appearing stuck.
Our experience with 5+ projects for foldables and tablets shows that quality Multi-Window support increases retention by 10–15% (based on internal client analytics). We use a certified environment for testing on real devices in Firebase Test Lab. See the official Android Developers documentation for more details on Multi-Window support.
Conclusion
A Multi-Window-ready app is not a luxury but a user requirement on Android. We configure not only Split-Screen but also PiP, Freeform, and adaptation for foldable screens. Contact us for a project diagnosis—we'll assess the scope and propose a solution tailored to your stack.