Your App Could Use a Secondary Screen!
summary
Explains how to run Android apps on a secondary display using DisplayManager and WindowMetrics API, and how to launch an activity onto another screen with ActivityOptions.setLaunchDisplayId plus flags ACTIVITY_LAUNCH_ADJACENT and FLAG_ACTIVITY_NEW_TASK. Covers resizableActivity behavior across API levels (600 dp threshold), why to use activity rather than application context, lifecycle differences (full recreation on significant size changes), and the need to save UI state. Shows Zebra workstation connect hardware plus an agent that accepts managed configurations or JSON to set mirror/extend, resolution and shortcuts.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:08Why apps need secondary screens
- 3:20Secondary screens use cases
- 5:07Coding multi-window support
- 9:02DisplayManager for displays
- 11:30Activity lifecycle on secondary displays
- 13:37Preserving UI state
- 15:04Zebra Workstation Connect overview
- 17:54Q&A
related talks
19mYour app could use a secondary screen!
33mOptimize your app for large screens
28mBuilding an app for the Multi-Device world
35mBuild apps for foldable, multi-display, and large-screen devices
39mBring Optimised Experiences to the Big Screen
15mDo more with multi-window and activity embedding
40mAndroid Large Screen:How your app can power a workstation
40mOptimize your app for large screens