ref.google.android-adaptive-layout · official-system
Build adaptive apps — Android Developers
Current Android platform implementation guidance for adapting navigation patterns and pane layouts to window posture and size class rather than device labels. It covers compact, medium, and expanded window classes plus folding-posture APIs in Jetpack Compose.
https://developer.android.com/develop/ui/compose/layouts/adaptive/get-started-with-adaptive-apps
What this source teaches
- Add capability/window-class decisions to the platform matrix: navigation rail vs. bottom bar vs. drawer should derive from window size class, not device type.
- Distinguish list-detail, supporting-pane, and feed pane layouts by window class and user task, not by hardcoded breakpoints.
- Keep Compose-specific APIs as implementation evidence, not web requirements; extract the capability-based decision model for cross-platform use.
Where AwesomeDS applied it
rule.adaptation.capability-first— Adapt by capability, not device labelrule.foundations.platform-literacy— Respect platform grammar before brand divergence
Implementations and artifacts
No directly linked artifacts.
Caveats & anti-imitation
Transfer window-class and capability-based adaptation patterns; do not import Android-specific dp thresholds or Compose APIs as cross-platform requirements.