IssueTracker

Based on the list of folding features, its possible to determine well-named postures.

The best named posture that also has accompanying UX guidance is "tabletop" for foldables, and in most cases the current posture is "flat" for non-foldable devices.

This is derivable from the list of folding features, but having a more explicit API to recognize postures would make it easier to handle different situations.

material3-adaptive has implemented something similar to this idea as part of the WindowAdaptiveInfo here: https://cs.android.com/androidx/platform/frameworks/support/+/androidx-main:compose/material3/adaptive/adaptive/src/commonMain/kotlin/androidx/compose/material3/adaptive/Posture.kt;l=41;drc=b31b9041ecfdb808471ed6ce3e56293a4008e093

Since the folding features are themselves represented as an asynchronous flow, the posture should similarly be represented.