How to achieve the best experience for Multi-Window
summary
Targeting Android N turns multi window on by default and forces concrete changes: split screen picture in picture and free form modes appear and common widgets resize unexpectedly. Expect appbar drops 56→48 dp and FAB auto shrinks below 470 dp, lifecycle churn where onPause/onResume runs often so do not unregister onPause and avoid heavy work in onResume. Manifest can opt out with resizableActivity or enable adjacent windows via FLAG_ACTIVITY_LAUNCH_ADJACENT, use CoordinatorLayout behaviors or resource qualifiers to implement responsive breakpoints and test with and without N.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 1:43What is multi-window
- 4:29Design impacts of multi-window
- 14:19Upgrading apps for multi-window
- 29:12Best experience strategies
- 37:34Testing and future considerations
related talks
01h 31mMulti-Window and Your App
28mBuilding an app for the Multi-Device world
15mDo more with multi-window and activity embedding
46mA developer's guide to large screens readiness
47mOptimizing Android apps for desktop experience
47mDual-Screen & Multi-Posture: Let’s Rethink Mobile Apps
39mBring Optimised Experiences to the Big Screen
22mConsiderations for Multi-Device Support