Canonical layouts and visual hierarchy: Designing for larger screens
summary
Canonical layouts claim to get apps to tier two large screen quality by offering three concrete patterns and ready code. Use activity embedding (Android 12L+, one XML plus one line of runtime registration) for multi‑activity list‑detail, or SlidingPaneLayout (handles folds/hinges) for views fragment splits. For Compose use the two‑pane composable in accompanist and window‑size classes, and for feeds use a lazy vertical grid with ≥240dp columns. Samples and guidance live on GitHub and Material Design links.
AI-written summary · about
chapters (9)
- 0:00Intro
- 0:51Large Screen App Quality Tiers
- 1:01Canonical Layouts
- 3:37Window Size Classes
- 7:41Activity Embedding Configuration
- 8:41SlidingPaneLayout
- 12:04Resource Qualifiers
- 15:55Feed Column Logic - Compose
- 17:03Feed Column Logic - Views
related talks
18mCanonical layouts and visual hierarchy: Designing for larger screens
37mBuilding Responsive UIs for tablets, foldables, and other devices
33mOptimize your app for large screens
14mDesigning apps for large screens
40mOptimize your app for large screens
34mResponsive UIs for tablets, foldables, and other devices.
20mDo’s and don’ts: Mindset for optimizing apps for larger screens
18mCompose: Implementing responsive UI for larger screens