@Yingding Wang sounds like your issue is unrelated, but I ended up implementing this to let me test various config options for ScalingLazyColumn.

Restarted my old Macbook pro to play with compose wear during holidays and with EE A 9 75% of the time when I start the app there’s a dialog with Process wear is running Do you want to kill the process. And even checking don’t ask again does nothing and it comes back.

hey guys, Is there any equivalent of

BottomSheetScaffold

for wear? Can I safely import both:

androidx.wear.compose:compose-material

and

androidx.compose.material:material

to my project and use only

BottomSheetScaffold

from the non wear one??

Performance of Wear OS apps built with Compose is the topic that come up here time to time, so want to share performance guide that we recently published: https://developer.android.com/training/wearables/compose/performance on how to configure, develop and test performance in your apps, including useful adb commands from @Steve Bower [G] for baseline profiles 📊

How do you guys deals with older watches with bottom chin like the moto 360? I think that I should just disable support for the in Play Console but I still fear the Play Store nice Wear review team reject the app as they might test it even with the excludes.

Compose for Wear OS 1.1.0-alpha03 was released yesterday. Release notes are here. We have added a new

Outlined

style for `Chip`s and `Button`s and we have added overloads to allow developers to override

Button

shapes. We have also corrected an issue with excess padding in the

ToggleChip

this will leave more space for the label slot - as a result if you have screenshot tests for ToggleChip`s these may need updating.

Is there already a standard way to add haptics to

LazyColumns

? My workaround solution that I implemented in the past don't work very well

ScalingLazyColumn

could use

animateItemPlacement

Modifier support. https://issuetracker.google.com/issues/241957435

Compose for Wear OS 1.0.1 and 1.1.0-alpha04 were released yesterday. Both contain a bug fix for an issue with

ScalingLazyColumn

not completing initialisation if the list has 2 items. But the change we would like to draw your attention to is an accessibility driven change the default theme colors in 1.1.0-alpha04 [2183442] as this will have a UI impact and might cause some screenshot tests to need to be regenerated.

If it's useful for anyone else, I'm taking a stab at using Paparazzi for A11y testing. https://github.com/google/horologist/pull/524

If anyone has a confirmed need for paging-compose with ScalingLazyColumn, let me know. Say infinite or paged results (email inbox, messages) I've a prototype of this for Horologist (draft PR) but it's not clear we expect this to be a typical use case. So any signal from community could make the case. The integration is very simple and straight forward.

Hi, is it possible to use entry/exit animations using Compose for Wear OS?

Hi, I'm wondering if there's a way to disable the swipeToDismiss action for a fitness screen, similar to the workout in progress screen on the google fit app. I intend to add a button to do the same, but swiping doesn't really work for the UI I'm planning

Is anyone developing on something other than a silicon based Mac & using the Wear emulator?

Compose for WearOS 1.0.2 and 1.1.0-alpha05 released last night. Just small change this time. Both contain a bug fix for the z-order of the items in the Scaffold so that the indicators (Position and Pagination) sit on top of the Vignette. The alpha also includes a small a11y/talkback improvement for the Slider.

We've added Jankstats, Macrobenchmark startup tests, Baseline profile, and some custom Trace metrics to the media-sample in Horologist. If you want to test out the real impact of these on performance or testing, please ping me, happy to discuss. https://github.com/google/horologist/pull/565

StartupBenchmark_startup[compilation=BaselineProfile]
timeToFullDisplayMs   min 1,468.5,   median 1,522.9,   max 1,585.2
timeToInitialDisplayMs   min   650.4,   median   678.5,   max   762.3

StartupBenchmark_startup[compilation=None]
timeToFullDisplayMs   min 3,618.2,   median 3,845.0,   max 4,448.7
timeToInitialDisplayMs   min   806.8,   median   901.9,   max 1,069.0

Hey, we've recently added a

SectionedList

component to Horologist that should help building screens divided in sections and controlling the sections states individually. There is a video of the sample screen in this PR. I hope that you find it helpful.

Hi, I recently wrote an article about our company moving to Jetpack Compose, there is also a large section on how implemented Wear Compose - https://proandroiddev.com/auspost-delivers-on-jetpack-compose-892f609774fd

Sorry not fully wear compose related but discovering https://issuetracker.google.com/issues/235538840 the hard way. Can someone confirm that removing the

<data android:scheme="wear" android:host="*" />

Will not have impact on previous Android version and still work with Wear OS 1 (That I still support for now)?

Is there any plans to have the PositionIndicator highlight configurable? I'm facing a small issue due to rounding leading to double state update leading to blinking of the indicator. (Like a volume bar that send the volume to a remote device then receive the updated volume that is a little different and update the state).

Another one about Curved text / Timetext it seems they do not support the shadow part of the text styles that can be useful to increase a little contrast over images. My other workaround would have been to use a dark background on the timetext but I can't figure out what I could put in

startCurvedContent

and

endCurvedContent

to add a round borders on each side like a curved chip.

And one last, I was not able to configure an emulator for Wear 3 to provide a 3rd multi function button. Is this possible?

This just landed, so should be in Paparazzi 1.1

Compose for Wear OS 1.1.0-alpha06 was released yesterday (2022-09-21). The main addition in the release is

Modifier.scrollAway()

that can be used to scroll

TimeText

away when scrollable content is scrolled up. This is based on the Horologist

Modifier.fadeAway()

, big thanks to @yschimke for that.

Not strictly compose related but I was hoping that migration to Compose would have fixed it. I get ANR on the watches

android.hardware.display.DisplayManagerGlobal.getDisplayInfo
Broadcast of Intent { act=android.intent.action.SCREEN_OFF }

Thread

"main" tid=1 Blocked

at android.hardware.display.DisplayManagerGlobal.getDisplayInfo (DisplayManagerGlobal.java:146)
  at android.view.Display.updateDisplayInfoLocked (Display.java:1251)
  at android.view.Display.getState (Display.java:1206)
  at android.view.ViewRootImpl$1.onDisplayChanged (ViewRootImpl.java:1604)
  at android.hardware.display.DisplayManagerGlobal$DisplayListenerDelegate.handleMessage (DisplayManagerGlobal.java:767)
  at android.os.Handler.dispatchMessage (Handler.java:106)
  at android.os.Looper.loop (Looper.java:246)
  at android.app.ActivityThread.main (ActivityThread.java:7690)
  at java.lang.reflect.Method.invoke (Native method)
  at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:593)
  at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:995)

Since I do not register that intent myself any idea what does and how to prevent it?

Cannot wait to get the Pixel Watch for compose wearos dev 😄

The Compose for Wear OS team are please to announce the release of 1.1.0-alpha07. There are a couple of items that I would like to call out for attention. Firstly we have added animated

Checkbox

,

Switch

and

RadioButton

toggle controls. Secondly we have added a new experimental Placeholder API which gives coordinated Placeholder, Shimmer and Wipe-Off effects. More in the thread.

I preordered the Pixel Watch, cannot come soon enough 😮😮😮

I used to have a moto360 sport, which I gave away to my younger sister, cannot wait for the new one