Horologist 0.5.16 which is based on Wear Compose 1.3.0-beta02, has a couple of features (`AppScaffol...

# compose-wear

[yschimke]

Horologist 0.5.16 which is based on Wear Compose 1.3.0-beta02, has a couple of features (AppScaffold and responsive() ScalingLazyColumn) that should help build for larger devices on the market, such as Mobvoi which is 233dp.

[yschimke]

See https://google.github.io/horologist/compose-layout/

[yschimke]

This sample should be enough to make your screens responsive, and handle TimeText etc.

[yschimke]

import com.google.android.horologist.compose.layout.AppScaffold
import com.google.android.horologist.compose.layout.ScalingLazyColumn
import com.google.android.horologist.compose.layout.ScreenScaffold
import com.google.android.horologist.compose.layout.rememberColumnState
import com.google.android.horologist.compose.rotaryinput.rotaryWithScroll

AppScaffold {
    SwipeDismissableNavHost(
        startDestination = "home",
        navController = navController
    ) {
        composable(
            "home",
        ) {
            val columnState = rememberColumnState(ScalingLazyColumnDefaults.responsive())
            ScreenScaffold(scrollState = columnState) {
                ScalingLazyColumn(
                    modifier = Modifier
                        .fillMaxSize(),
                    columnState = columnState
                ) {
                    items(100) {
                        Text("i = $it")
                    }
                }
            }
        }

[yschimke]

As a sample, these are the screenshot tests against various devices.

[yschimke]

image.png

[yschimke]

If your app gets Play Store rejected for clipped text, then read https://developer.android.com/design/ui/wear/guides/behaviors-and-patterns/clipping, but consider using these Horologist APIs to avoid the hassle. (bumping to top level for visibility)