screenPadding

Insets the content by the surface's unsafe regions and then by its adaptive screenPadding, in one call. Use this instead of padding(tokens.screenPadding).

A raw screenPadding is not enough on real hardware: on a landscape phone the display cutout and the gesture bar eat into the same edge, on iOS the notch and home indicator do, and on a television the panel physically clips the border. Applying only the token clips content on all three. This applies WindowInsets.safeDrawing first — which covers cutouts, system bars and the IME on every platform that has them, and is empty on desktop and web — then the token on top.

Column(Modifier.screenPadding()) { /* never under a notch, never off the edge of a TV */}
LazyColumn(Modifier.screenPadding(vertical = false))   // let the list scroll under the status bar

ponytail: the TV case rides on screenPadding alone, which is already overscan-safe (48dp+), not on AdaptiveTokens.overscanPadding. Adding both would double-inset. overscanPadding is for full-bleed surfaces that opt out of this modifier entirely — a hero image that must reach the edge but keep its caption out of the clipped band.