https://play.google.com/store/apps/details?id=com.refect.hue4wear It’s finally here 🙌 If anyone has Philips Hue products, would love any feedback. This is my first Jetpack Compose application, and the application is 100% Compose. The initial build is somewhat limited, but still offers full [local] control over all of your Philips Hue lights (on/off, color, and brightness). I am opening a beta track tomorrow and will be releasing automatic bridge finding, color temperatures, groups/rooms, scenes, and remote auth soon! Watchface complications, Tiles, and Hue Entertainment integration are also on the way 💡 Much thanks to this community! (If this kind of content isn’t allowed, I can remove this post)

My Home navigation target is dynamic, because it has a ViewPager What is the right way to navigate to the top of the stack? I ended up using a while loop and popBackStack, because it doesn't see to work if I don't know the route exactly. cc @Steve Bower [G]

fun navigateToPlayer(clearBackstack: Boolean = true) {
        val route = NavigationScreens.Player.route + "?page=0"
        if (clearBackstack) {
            while (navController.popBackStack()) {}

            navController.navigate(route)
        } else {
            navController.navigate(route)
        }
    }

What is the library approach to dealing with @DimenRes in APIs? Does compose-wear always expect resource values to be resolved outside of the APIs? cc @John Nichol @saryong

Compose for Wear OS Alpha16 has been released including ProgressIndicators. Snapping on Pickers and some enhancements for ScalingLazyColumn with more to come in the following releases

How does dialog get the value in item across domains? Click in item to open dialog. Because dialog cannot appear in onclick {}, the value in item cannot be modified after onclick {} operation.

I have a question related more so around distribution of an embedded wear app (not sure if this is the correct forum since this is more for jetpack compose), but the developer docs aren't very clear or up to date anymore. I’ll try here first and perhaps someone can direct me accordingly.

Picker supports adsorption, celebrate!!!

Hello, it looks like we don't have a channel for WearOS Watch Face developers. Is anyone busy making one here?

When I use scalinglazycolumn (autocentring = false), how can I make this page automatically scroll to the top. thank you.

As I'm rewriting a 6 years old Watch Face project on top of AndroidX Wear Watchface, with the intent of publishing it on the Play Store this time, I'm wondering why we have a Compose backed API for Tiles in Glance, but we don't for WatchFaces. I think it'd be very helpful to have access to

remember { … }

,

State

, and other Compose facilities for interactive and animated Watch Faces. Is there a reason we don't have such an API? I'd think maybe there would be some performance concerns, or other potential issues, or maybe just bandwidth? I'm wondering about that because I am pondering about hacking around to use Compose to control what gets rendered on my Watch Face.

Curious is anyone has experience with Lottie in Wear Compose. Well documented the binary and runtime differences. https://github.com/airbnb/lottie/blob/master/android.md#what-is-the-impact-of-lottie-on-apk-size Ultimately this is an app/UX decision, I'm happy to make.

Hello - time for your regular fortnightly reminder that there is a new Compose for Wear OS Alpha18 release. Updates for Dialogs, Position Indicator and ScalingLazyList autoCentering mode as well as UX updates and a sample RSB (Rolling Side Button) scroll+fling handler

Hello, can we expect the https://github.com/androidx/androidx repo to accept AndroidX Wear contributions soonish?

I've got a question about using Scaffold with Navigation. I'm switching my PositionIndicator scroll state whenever the navigation NavBackStackEntry changes. The default for this doesn't appear to work, I'm guessing because my scroll type is always ScalingLazyListState state, while other tests change between different scroll types. I've worked around it by wrapping it with

key(currentBackStackEntry?.destination?.route)

but surprised I needed to. Is this expected? Am I doing something wrong with when I'm accessing a state field? Or is it a bug in PositionIndicator?

The UiAutomator code in Compose Macrobenchmarks makes me a bit sad. I do wonder whether there could be say a Compose aware higher level API, since I suspect we are going to replicate various bespoke implementations of actions scroll through list.

Hi, I'd like to ask you to use Page Viewer (Page Indicators). Are there still Page Viewer (Page Indicators) that are compatible with wearables? I'm using an acompanist-pager because I can't find a way. I'd like to ask if this is the right way.

Is there a way to dynamically disable the swipe to dismiss gesture? My use case is that I am using the HsvColorPicker composable from https://github.com/skydoves/colorpicker-compose and it works great, except when I start dragging to the right 😕

Not sure if anyone else uses fastlane to automate play store releases, but if you do this screenshot strategy, fixes the screenshots to be acceptable for the Play Store https://github.com/yschimke/rememberwear/blob/main/wear/src/androidTest/kotlin/com/google/wear/soyted/fastlane/WearScreenshotStrategy.kt

private fun screenshot(screenshotName: String, block: @Composable () -> Unit) {
        composeTestRule.setContent {
            RememberTheMilkTheme {
                Scaffold(timeText = {
                    TimeText(timeSource = FixedTimeSource)
                }) {
                    block()
                }
            }
        }

        composeTestRule.onRoot().assertIsDisplayed()

        val context = InstrumentationRegistry.getInstrumentation().context
        val isScreenRound = context.resources.configuration.isScreenRound
        Screengrab.screenshot(screenshotName, WearScreenshotStrategy(isRoundDevice = isScreenRound))
    }

A question about Compose Tests building on Wear Compose / Material. I ended up with a test like

@Test
    fun testAutoHide() {
        composeTestRule.setContent {
            VolumePositionIndicator(
                modifier = Modifier.testTag(TEST_TAG),
                volumeState = { volumeState },
                autoHide = true
            )
        }

        val positionIndicator = composeTestRule.onNodeWithTag(TEST_TAG)

        positionIndicator.assertDoesNotExist()

        volumeState = volumeState.copy(current = 51)

        composeTestRule.mainClock.advanceTimeByFrame()
        composeTestRule.mainClock.advanceTimeBy(500L)

        composeTestRule.onRoot(useUnmergedTree = true).printToLog("testAutoHide")

        positionIndicator.assertIsDisplayed()
    }

Compose for Wear OS Alpha19 landed yesterday. It includes a new take on the

CurvedRow

CurvedLayout

API including a DSL for describing curved components. Also some APIs moved from experimental to public (such as SwipeToDismissBox) with some minor API updates.

PositionIndicator

has had some updates to allow control over positioning, better handing of unscrollable contents, etc. Finally some UX updates to

ScalingLazyColumn

scaling parameters and

CircularProgressIndicator

size, padding and track colors.

I got some

Rendering sandbox error

to use the compose preview with ui-tooling:1.2.0-alpha06 in Bumblebee. Really like

Devices.WEAR_OS_SQUARE

and

Devices.WEAR_OS_SMALL_ROUND

from compose 1.2.0 in Preview By turning off the rendering sandbox seems to solve the issue, is it recommended to do so? My apology if it is an off-topic question.

@Preview(
    apiLevel = WEAR_PREVIEW_API_LEVEL,
    uiMode = Configuration.UI_MODE_TYPE_WATCH,
    backgroundColor = WEAR_PREVIEW_BACKGROUND_COLOR_BLACK,
    showBackground = WEAR_PREVIEW_SHOW_BACKGROUND,
    showSystemUi = false, // the android system bar on top
    device = Devices.WEAR_OS_SQUARE
)
@Preview(
    apiLevel = WEAR_PREVIEW_API_LEVEL,
    uiMode = Configuration.UI_MODE_TYPE_WATCH,
    device = Devices.WEAR_OS_SMALL_ROUND
)
@Composable
fun WearAppPreview() {
    WearApp()
}

Are there any libraries for displaying graphs / charts, while using compose? Thanks

Why does scalinglazycolumn constantly refresh the item when the page scrolls？ Thanks!

We thought it’d be a cool idea to also write a wearable version of our app, and so it begins!

Is there any reason why rotary input on the wear emulator doesnt seem to scroll lists?

Compose for Wear OS Alpha 21 is out. Release notes can be found here and there are a lot of changes with some new APIs for curved modifiers as well as a lot of API tidy up as we prepare for API freeze and Beta release. More specifics in the thread.

Regarding the ToggleChip in Compose Wear OS Alpha 21, switchIcon() returns now an ImageVector. As i use the following code, the switch Icon doesn’t show anymore in ToggleChip.

ToggleChip(
    modifier = modifier,
    checked = checked,
    toggleControl = {
        ToggleChipDefaults.switchIcon(checked = checked)
    },
    onCheckedChange = {
        checked = it
    },

Is there any additional steps in

toggleControl

I will need to display the switch icon as that of Alpha 20?

Anyone using Lottie for animations on Wear? Any issues?

Have you ever met this error in wear-compose 1.0.0-alpha21 and accompanist pager(above 0.21.3-beta) environment?

java.lang.IllegalArgumentException: Inconsistency between the count of nodes tracked by the state (0) and the children count on the SubcomposeLayout (2). Are you trying to use the state of the disposed SubcomposeLayout?

I thinks it is a same issue on compose issueTracker accompanistIssue I need version 1.0.0-alpha21 to use edgeSwipToDismiss in my pagerScreen. According to the issue tracker above, it seems that the version of compose need downgrade. Does anyone know the solution?

Hello ! I'm building a wear os app using compose, and using

SwipeDismissableNavHost

I've found that the swiping gesture is ignoring the

BackHandler

inside the composable. For example, if my nav graph is: A -> B -> C, and the swipe from C should redirect to A. I think I have to custom some behavior of the SwipeToDismissBox, but I'm not sure how. Any help is appreciated!

composable(
    Paths.WORD,
    arguments = listOf(navArgument("language") { defaultValue = "EN" })
){ navBackStackEntry ->
    BackHandler() { navController.navigate(Paths.HOME) }
    CompleteWord(navController, listState, completeWordViewModel, navBackStackEntry.arguments?.getString("language")!!.toLanguage())
}

Slack Conversation