Making Apps adaptive with Material and Compose
summary
Concrete guidance about adapting apps with Material Design 3, Jetpack Compose, and the WindowManager window metrics: use calculateWindowSizeClasses to pick bottom nav vs rail vs permanent drawer, switch single vs dual pane, and handle fold posture and occlusion from display features. A Compose sample called reply implements these strategies (including hinge spacers and movableContent API) and demonstrates them across phone tablet desktop and foldables. Google cites 250 million+ large‑screen devices and an early compose adaptive library in active preview.
AI-written summary · about
chapters (28)
- 0:00Intro
- 1:17What is Adaptive?
- 2:23Android Ecosystem
- 3:25Material x Adaptive
- 3:52Anatomy of layout
- 4:29Compose x Adaptive
- 6:29Screen vs App Size
- 9:02Navigation & Body
- 9:17Material Navigation
- 9:52Select Navigation
- 10:27Deciding Content type
- 12:22Folding Features
- 13:19Making apps fold aware
- 14:03Fold Classification
- 14:40Reply sample with postures
- 15:12Update Navigation with Fold
- 15:31Hinge detection
- 15:53Adding Hinge Spacing
- 16:45Accompanist adaptive
- 17:55Pane divide strategy
- 18:30Moveable Content Apis
- 19:43User experience and Accessibility Improvements
- 20:00Continuity
- 21:13Ergonomics of Devices
- 22:08Accessible design
- 22:32Window Height for Ergonomics
- 23:06Recap
- 23:38Benefits of Adaptive app
related talks
33mBuild adaptive apps with Jetpack Compose
18mCompose: Implementing responsive UI for larger screens- 18mCompose: Implementing responsive UI for larger screens
29mAdapting Android Apps for Multiple Screens Compose-First Approach
01h 01mComposing large screens
35mBuild adaptive apps with Compose's new APIs
28mBuilding an app for the Multi-Device world
43mBuilding Accessible Apps with Jetpack Compose