Responsive UIs for tablets, foldables, and other devices.
summary
Optimizing for large screens increases engagement — Chrome sees an 18× rise in side‑by‑side use and Google Photos reports a 53% uptick in in‑app activity — and the concrete tools are: activity embedding (XML rules loaded via Jetpack App Startup, creates primary/secondary stacks, 30/70 split and minWidth 600dp example), SlidingPaneLayout (reuse fragments with two nav graphs, 300dp pane widths, call open() on phones), and Compose’s window size classes plus the two‑pane composable; follow 600/840dp buckets, avoid isTablet/smallestWidth, and preserve state across resizes and multi‑window.
AI-written summary · about
chapters (11)
- 0:00Introduction to large screens
- 1:50Why optimize for large screens
- 3:37App quality tiers explained
- 5:42Designing for screen buckets
- 8:32List detail canonical layout
- 9:15Activity embedding for multiple activities
- 15:23SlidingPaneLayout for fragments
- 23:54Window size classes in Compose
- 27:27Common mistakes to avoid
- 31:42Multi-window and lifecycle handling
- 34:00Q&A
related talks
37mBuilding Responsive UIs for tablets, foldables, and other devices
51mBuild Responsive UI in Android
33mOptimize your app for large screens
14mDesigning apps for large screens
21mForm Factors #AskAndroid
18mCompose: Implementing responsive UI for larger screens
38mOptimize your app for large screens
14mImplementing Android apps for all screen sizes