Deep dive into size configuration changes
summary
Large-screen and multi-window use makes window size change frequently and unpredictably; an example run shows activity restarts 4 vs config changes 100+, so relying on Activity restarts is unsafe. Use Jetpack WindowManager to get the usable Window size and hide inset complexity, and use view callbacks (or Compose’s LocalConfiguration / Window Size Classes) to observe changes. The demo counting tool proves view-level callbacks fire across API levels and the WindowManager approach reliably measures sizes and works.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:03What is size configuration change
- 2:31Large screen size change issues
- 7:27Window vs screen size
- 10:18Restart activity on config change
- 13:12Screen size and insets relation
- 21:05Accurate window size detection
- 24:10Handling config change notifications
- 27:43ビューのonConfigurationChanged活用
- 30:57View and activity implementation
- 32:24Compose size change detection
- 33:48WindowSizeClass library
- 36:41Summary and key points
related talks
30mDeep Dive Into Size Configuration Changes
32mDeep dive into size configuration changes
33mOptimize your app for large screens
24mOptimize your app for large screens
40mOptimize your app for large screens
46mA developer's guide to large screens readiness
28mBuilding an app for the Multi-Device world
38mOptimize your app for large screens