Deep Dive Into Size Configuration Changes
summary
Explains that size configuration values represent an activity window, not the physical screen, and that insets and DPI rounding produce concrete bugs (Pixel 7 Pro rounding can leave a one‑pixel gap). Recommends using WindowMetricsCalculator / AndroidX Window to get exact window metrics, relying on localConfiguration.current in Compose because it updates via view callbacks, and installing a small utility view that overrides view.onConfigurationChanged for reliable notifications across API 30–33; notes API24, 30–33, and 34 behavioral differences.
AI-written summary · about
chapters (9)
- 0:00Introduction to size configs
- 2:18What size configs represent
- 8:28Inset and rounding issues
- 15:12Accurate window size solutions
- 17:18Activity recreation behavior
- 19:26Significant vs insignificant changes
- 21:33Handling config changes
- 24:00Compose and API 34 updates
- 25:24Key recommendations
related talks
30mDeep Dive Into Size Configuration Changes
41mDeep dive into size configuration changes
32mDeep dive into size configuration changes
25mChaining Jetpack Compose modifiers beyond intuition
45mSize Matters: How to Measure and Reduce Android App Weight
33mBest Practices for Storing Data in BigQuery
09mStorage: managing billions of objects
27mRequest and Conquer: Exposing Cross-Origin Resource Size