Why is adaptive layout a nightmare?
summary
Adaptive layout causes concrete friction: moving navigation and FAB out of screen-level scaffolds breaks existing app module boundaries, window size classes are global not per-subcomponent, and the new scaffolds are alpha and changing. The talk uses window insets, WindowManager and the two new scaffolds (list‑detail and supporting‑pane) to migrate a production conference app, reworks component modules, creates compact/medium variants, and implements navigation‑suite scaffold; result: it runs but requires workarounds and architecture changes before it’s safe for production.
AI-written summary · about
chapters (14)
- 0:00Adaptive layouts introduction
- 1:11Multiform factor issues
- 3:40Navigation and module problems
- 5:28Tools and limitations
- 10:51New adaptive scaffolds
- 12:13Case study: conference app
- 13:40Rebuilding component architecture
- 17:36Landscape mode adaptation
- 21:50Implementing adaptive navigation
- 25:02Pane and list detail scaffolds
- 31:31Material Design conflicts
- 33:38Floating action button challenges
- 36:54Window size class limits
- 39:00Conclusion and future
related talks
38mWhy is Adaptive Layout a Nightmare?
33mBuild adaptive apps with Jetpack Compose
37mUI Layer Architecture for Adaptive Apps
44mAccessible Development: Customize Only When Necessary
49mNavigation Component, feedback from the trench
27mLayout Saga - in the web application era
38mCreating adaptable layouts using Trait Collections and Container Views
14mNavigation Compose on every screen size