Is it possible to use

ComposeTestRule

for UI automation when generating baseline profiles? UiAutomator does not really seem to work that well with compose+wear (e.g.

scrollUntil

does not detect scrolling), and I'm wondering if Compose's better UI testing APIs could be used here I tried to use

createEmptyComposeRule

but that does not seem to work either ("No compose hierarchies found in the app")

Can someone explain what's going on here with horizontal scrolling? I'm seeing an issue where scrolling an element horizontally sometimes just triggers the system activity swipe-to-dismiss action instead of scrolling. This happens almost all the time on my real device (Galaxy Watch 5) and a bit less frequently in an emulator. It kind of feels like there's some race condition in

scrollable

implementation that sometimes passes drag gestures to the activity and some times not. Here's a minimal sample:

class MainActivity : ComponentActivity() {
    override fun onCreate(savedInstanceState: Bundle?) {
        installSplashScreen()
        super.onCreate(savedInstanceState)
        setContent { WearApp() }
    }

    override fun onTouchEvent(event: MotionEvent?): Boolean {
        Log.d(TAG, "onTouchEvent: $event")
        return super.onTouchEvent(event)
    }
}

@Composable
fun WearApp() {
    MyTestAppComposeTheme {
        Box(
            modifier = Modifier.fillMaxSize().padding(horizontal = 8.dp)
        ) {
            val offsetX = remember { mutableFloatStateOf(0f) }
            val scrollState = rememberScrollableState {
                offsetX.floatValue += it
                it
            }

            Box(
                modifier = Modifier
                    .fillMaxRectangle()
                    .border(width = 1.dp, color = Color.White)
                    .scrollable(scrollState, Orientation.Horizontal)
                contentAlignment = Alignment.Center
            ) {
                Text(offsetX.floatValue.toString())
            }
        }
    }
}

This renders a box that is horizontally swipeable. As far as I know it should never let the activity swipe-to-dismiss trigger as long as the scrolling gestures start inside the box, right? Defining horizontal scroll semantics mostly fixes this; for example adding this after

.scrollable

in the above snippet

.semantics {
    horizontalScrollAxisRange = ScrollAxisRange(
        { offsetX.floatValue }, { 100f /* dummy value */ })
},

Is it a bug or should this be working without the semantics modifier? I know horizontal scrolling has been discussed many times here but I could not find this particular issue anywhere

Hi all - I'm delighted to announce that the Wear Compose team has released 1.5.0-beta01, the first beta release for the Wear Compose Material3 library. Additional API changes in this release: the hierarchical focus API now splits the functionality between modifiers for the focus handling and a new LocalScreenIsActive composition local that can be checked to tell if a screen is the currently active one; SwipeToReveal has been updated so that the experimental Foundation API is now deprecated and those parts that are still used have been migrated to the material and material3 libraries - the release notes give more details on this iteration, which removes the SwipeToReveal DSL and makes use of slots for primary, secondary and undo actions. Bug fixes: performance improvements to ScrollIndicator and LocalReduceMotion; fixed issues with EdgeButton and TransformingLazyColumn animations; updated motion of indeterminate CircularProgressIndicator; SwipeDismissableNavHost focus issue addressed; corrected the default alignment for ListHeader and ListSubHeader. Please also see the release notes for a summary of the new components and features, as well as more details on the items called out above - thanks.

Hi all - we have released 1.5.0-beta02 for Wear Compose, including fixes to TransformingLazyColumn and SwipeToReveal - please see the release notes for more details, thanks.

I was so much hoping for a beta version of the material 3 compose, I guess it is maybe for next year then 😄

Anyone from the wear-compose team ? Why is this method

private

? Will this be available in a future update ? Because at the moment, if we want to change the sensitivity, we must use the other method that takes a

ScrollableState

and provide a

LayoutInfoProvider

on our own. Also, we cannot customize the sensitivity beyond these 2 values that are HIGH and DEFAULT

@Composable
    private fun snapBehavior(
        scrollableState: ScrollableState,
        layoutInfoProvider: RotarySnapLayoutInfoProvider,
        snapSensitivity: RotarySnapSensitivity,
        snapOffset: Dp,
        hapticFeedbackEnabled: Boolean
    ): RotaryScrollableBehavior

Am I reading this correctly that watch faces that want to run/render their own UI are deprecated?

Hi all - we have released 1.5.0-beta04 for Wear Compose, including some bug fixes - please see the release notes for more details.

Hi all - we have released 1.5.0-beta05 for Wear Compose with some more bug fixes - please see the release notes for more details.

Sorry, this isn't about Compose, but just some piece of WearOS feedback, maybe this can be passed on to people working on the OS. Notifications about apps that are disabled, or permissions being revoked -> on the watch this is intrusive and utterly useless 🙂 Not sure if there's a setting to disable them (if not, please add one) but they should be disabled by default. (In fact, even on the phone, this is very dubious that this brings any value). There you go, just my 2c.

1.5.0-beta06 has been released https://developer.android.com/jetpack/androidx/releases/wear-compose#1.5.0-beta06

And now 1.5.0-rc01 has been released with some more bug fixes (especially to TimePicker where some internationalisation bugs had been found and now fixed). https://developer.android.com/jetpack/androidx/releases/wear-compose#1.5.0-rc01

We've released 1.5.0-rc02 with small a TimePicker bug fix - https://developer.android.com/jetpack/androidx/releases/wear-compose#1.5.0-rc02

Horologist 0.8.2-alpha adds a new API for capturing a Composable to a Bitmap for use in Tiles. Might be useful for reusing assets such as charts, between your App and Tiles.

private suspend fun circleCompose(): ImageBitmap? = 
        renderer.renderComposableToBitmap(DpSize(100.dp, 100.dp)) {
            Box(modifier = Modifier.fillMaxSize(), contentAlignment = Alignment.Center) {
                Canvas(modifier = Modifier.fillMaxSize()) {
                    drawCircle(Color.DarkGray)
                }
                FilledIconButton(onClick = {}) {
                    Text("\uD83D\uDC6A")
                }
            }
        }
...
addIdToImageMapping("circleCompose", circleComposeBitmap.toImageResource())

Hi all - I'm delighted to announce that Wear Compose 1.5.0 is now released, see https://developer.android.com/jetpack/androidx/releases/wear-compose#1.5.0 for the full release notes.

There is an Wear OS #AskAndroid tomorrow , come and chat and ask some fun questions.

Hi everyone! If you have missed, we are hosting the Wear OS Spotlight Week this week: https://android-developers.googleblog.com/2025/08/spotlight-week-wear-os.html?m=1 Some nice updates for Material 3 Expressive across Compose and Tiles, Credential Manager, Watch Faces and developer case studies from our friends at Todoist, Amoledwatchfaces and Dashlane 💚 And wrapping everything with an #AskAndroid livestream tomorrow as Yuri shared above :)

Hi, I am migrating to material3 my app to also add some material expressive components. Is there an equivalent of https://material-foundation.github.io/material-theme-builder/ for wear? I got most of the colors from my phone app but I am missing those:

primaryDim = TODO(),
    secondaryDim = TODO(),
    tertiaryDim = TODO(),
    surfaceContainerLow = TODO(),
    surfaceContainer = TODO(),
    surfaceContainerHigh = TODO(),
    outlineVariant = TODO(),
    errorDim = TODO(),

and I think

HorizontalPagerScaffold

is missing a TimeText param 😅

I think that just goes in the AppScaffold, or ScreenScaffold

and so you can't customize the time string if you use an horizontal or vertical pager?

You can, just nest the scaffolds?

I think that's why it's not there. Because you can put ScreenScaffold above the pager, or in each page, and I believe it will do the right thing

ah ok I though the design was one AppScaffold and then one of the sub Scaffold 👍

Do you have a sample that do that? https://developer.android.com/design/ui/wear/guides/get-started/apply#variable-font-axis

Hi all - we have released 1.6.0-alpha01 with the additional of new non-clickable `Card`/`TitleCard`/`AppCard`variations and also a new

TimePicker

type for displaying only Minutes + Seconds pickers. There are some important bug fixes that have been released in 1.6.0-alpha01 and also patched into a 1.5.1 release: •

SwipeDismissableNavHost

now marks in-progress transitions as complete for API 36 when swiping, which fixes an issue with lifecycles •

ScrollIndicator

direction now matches the content layout direction by default (so if you set

reverseLayout

in

ScalingLazyColumn

, it will be matched by the

ScrollIndicator

) • ScrollAway with

TransformingLazyColumn

now working correctly when navigating to another screen and back, so that

TimeText

will still scroll away as expected As always, please see the release notes for full details.

Not specifically wear-compose, but does include it. But @Garan Jenkin implemented a awesome Androidify feature https://github.com/android/androidify/pull/105 using Watchface Push

Hi all - we have released 1.6.0-alpha02 with the introduction of text-warping using the new

CurvedTextStyle

parameter

warpOffset

. There are some bug fixes that have been released in 1.6.0-alpha02 and also patched into a 1.5.2 release - please see the release notes for details, thanks.

Hi - we have released 1.6.0-alpha03 which implements missing support for verticalAlignment in TransformingLazyColumn (also patched into 1.5.3), adds a parameter to TimePicker so that you can specify the column to be focused initially, and we've removed an unused parameter (targetProgress) in the drawCircularProgressIndicator method. The computation for curved text width has been updated to take spaces before and after text into account (fixes issues with backgrounds not reaching the edge of the curved letters) - this latter change may break screenshots, particularly those with curved text on a background.

Quickly checking and it seems the m3 expressive shapes and wavy indicators are not present in Wear Compose ? Is there any plans for that or can we reuse them from the normal m3 ?