Maybe a navigation question, but is there an easy way to tell the difference between a destination becoming active by back (swipe or button) vs navigation (with launchtop)?

I have a design that requires a variable width chip. Chip with the slots seems to grab full width, assuming it's across the whole screen. Is there a particular form I should use to get the CustomChip described here? https://developer.android.com/training/wearables/compose/chips Or that's not supported by the Wear material components at the moment?

⚠️ Found a kinda dead link on that article in the "Compose for Wear OS" section: https://android-developers.googleblog.com/2022/05/whats-new-in-jetpack-compose.html It leads to https://android-developers.googleblog.com/2022/05/announcing-compose-for-wear-os-beta.html that looks empty.

Glad to share that today we released the first Beta of Compose for Wear OS! 🎉 You can read more about the announcement in blogpost: https://android-developers.googleblog.com/2022/05/announcing-compose-for-wear-os-beta.html Huge thank you for everyone who tried early versions, gave us feedback and helped to shape the APIs! There is also another release announcement inside this blogpost 🥚🙃 Hope you’re enjoying Google I/O, stay tuned for Wear OS content coming on Day 2 👀

Some Compose for Wear OS preview utilities from horologist https://github.com/google/horologist/pull/147/files#diff-9dc0d46485295a9dd95df35a83c430891488937f7cc1fafd0bbf08cd3b35c347

@WearPreviewDevices
@WearPreviewFontSizes
@Composable
@OptIn(ExperimentalHorologistAudioUiApi::class)
fun VolumeScreenPreview(
    @PreviewParameter(AudioOutputProvider::class) audioOutput: AudioOutput
) {

Another Horologist feature - WearNavScaffold. https://twitter.com/yschimke/status/1524825410068004864

@John Nichol What is the UX guidance for GoogleMaps? We use Vignette for content that might go to the edge. Maps seems to have similar case, would you suggest using CurvedLayout with a gradient to blur the edges for full bleed content like Maps?

Hello all. Did anyone encounter huge lag and FPS drop for the first ~5-10 seconds when a screen with ScalingLazyColumn is used? I switched to Column + .verticalScroll() and it's much better.

Before I ask the next one, please inform me if this is not the right place for these questions. I am trying to add a complication and glance tile for my app. Each of those would have the same logic: 1. get the location 2. do a network request with the result 3. update the complication/tile My main concern is that the get location from FusedLocationProviderClient is not synchronous, so 2 and 3 are in addOnSuccessListener. I am looking for some directions in how this is supposed to work. Currently I am trying to start a Worker to get the location and do the network request and then somehow this one should request an update on the UI. Is this the right way?

Another feature from Horologist - but hopefully more an example for Connecting Bezel/RSB scrolling with something not directly UI related. In this case volume control.

The Live Edit also works for wear?

Compose for Wear OS 1.0.0-beta02 is available - It includes a collection of UX improvements and bug fixes including Picker, HorizontalPageIndicator EdgeSwipe. and snappier ScalingLazyList snapping The main thing I want to bring your attention to is a change in UX bahaviour of Chip/CompactChip/ToggleChip/SplitToggleChip which will now default their size to fit their contents rather than default to full width of their parent.

Another blatant Horologist commercial, this time thanks to @Steve Bower [G] and the Wear OS UX team - some high quality full screen date and time pickers. https://google.github.io/horologist/composables/

With the introduction of Health Services on Wear OS and the arrival of the Pixel Watch in a few months I'm a bit surprised about the lack of guidance for Ambient Mode in Compose, which will probably be used by most fitness and medical apps to show some data during an exercise. Right now I am just setting a Boolean from onEnterAmbient() and onExitAmbient(), which then leads to hiding interactive UI elements and the progress indicator (which would otherwise update every frame). I do not handle the other methods (e.g. onUpdateAmbient()) at all; is that how it is supposed to be? It feels like I should do more. There is also a problem where Ambient Mode still is not working correctly or not as expected on the Samsung Galaxy Watch 4: When entering Ambient Mode, I receive almost no updates, so the time does not update every second (the heart rate does not update either, but that is probably an issue with the Health Services batching them despite being in Ambient Mode). At first I thought that might be an issue with Compose and handling Ambient Mode wrong (like updating the screen too often), but the Google Fit app has exactly the same problem while the Samsung Fit app works perfectly during Ambient Mode. I guess Google Fit doesn't use Compose yet and the Samsung Fit app probably has some special API access?

Quick question: To implement a horizontal pager (or carousel) on Wear Compose, do I use the ViewPager2 components or the HorizontalPager components (from accompanist)?

Hello, World! Is it expected that the Wear Compose preview don't work on AS Chipmunk?

I have a full screen horizontal pager (using Accompanist's

HorizontalPager

), and the default Activity's swipe to dismiss behavior "vaguely works" 🙂 By that I mean, if I swipe with a quick enough gesture, it works. If I swipe slowly, it doesn't. (not using

NavHost

or

SwipeToDismissBox

) Any idea/pointers?

Previously I was using Yuri's solution for rotaryInput. However, as wear-compose was raised to beta, that solution did not work. I replaced it with onRotaryScrollEvent and focusRequest, which were added to Alpha-15 in the past, and it seems to work normally now. Please let me know if you have any known issues or better suggestions regarding this.

val scope = rememberCoroutineScope()
val focusRequester = remember { FocusRequester() }
LaunchedEffect(Unit) {
    focusRequester.requestFocus()
}
Modifier
.onRotaryScrollEvent{
   scope.launch{
       scalingLazyListState.scollBy(it.verticalScrollPixels)
   }
   true
}
.focusRequester(focusRequester)
.focusable()

What I additionally found out about this is that focuseRequester() and focasable() must not be above onRotaryScrollEvent{}. • working

.onRotaryScrollEvent{
   scope.launch{
       scalingLazyListState.scollBy(it.verticalScrollPixels)
   }
   true
}
.focusRequester(focusRequester)
.focusable()

• not working

.focusRequester(focusRequester)
.focusable()
.onRotaryScrollEvent{
   scope.launch{
       scalingLazyListState.scollBy(it.verticalScrollPixels)
   }
   true
}

Compose for Wear OS Beta03 has been released. This includes changes to enable

ScalingLazyColumn

to work in @Preview and also a change in its default behaviour so that content will be Center rather than Left aligned by default. We expect this to be the final beta release.

I have a quick question regarding the differences between Accompanist and Horologist. The Accompanist is designed for Android in mind and Horologist is for Wear OS? They both are based on compose right? I was looking for Pager Layouts in Horologist, but it is still only available in Accompanist.

I found it rather difficult to us

compose-wear

with an

AppCompactActivity

on Wear OS, if i want to migrate to wear compose along side my view system code. The following steps are necessary: 1. the view code need to use

Theme.AppCompat.DayNight.NoActionBar

from MDC lib

com.google.android.material:material

2. use the AppCompatTheme Adaptor from the Accompanist

com.google.accompanist:accompanist-appcompat-theme

to copy over the AppCompat Theme to a MaterialTheme composable 3. Add wear compose dependencies, and also horologist dependencies I wish there is a codelab for this 🙂 I made an example project to demo this possibility that I can also migrate to compose-wear starting with new features along side view system code (https://github.com/yingding/wear-os-examples/tree/main/Wear3KtxPagerExample), would love to hear your thoughts on this.

@Yingding Wang For the codelab, is it specifically about introducing a first compose screen into an existing Wear app? I can't promise anything, but just like to understand the scope of what you are after and if it's slightly different what other material we already have. Or if it's important to have ways to share themes between android:theme and Wear MaterialTheme.

Just making sure I dont shoot myself in the foot further down the line. The wear foundation is additive to the regular one, meaning that Id be fine bringing the regular foundation into my wear integration, while also depending on and making use of the wear specific one to support curved modifiers, etc?

PSA: You should look at Paparazzi for your screenshot testing needs https://github.com/cashapp/paparazzi/

If anyone here also has a Tile for their app. I've added support to the Horologist project for Android Studio previews (via the Compose @ Preview annotation). Here shown previewing different devices (small round, large round, square) and font sizes.

I’m having an “issue” where, when opening a detail screen, the top item is displayed but the padding on the top is not respected, so the item is behind the clock. Is there a way to fix it?

@Tgo1014 @bod Curious about what each of your tech stack looks like? Compose obviously, but Coil for images? something else? Do you plan a tile for your app? Feel free to respond 1:1, or not at all.

Is there already a material-icon or material widget in wear os compose to show monk skin tone scale? (https://blog.google/products/search/monk-skin-tone-scale/)

I found a small bug, if you use

scrollBy

the

PositionIndicator

is not shown but if you use

animateScrollBy

instead, it shows (at least when calling inside the

onPreRotaryScrollEvent{}

. I'll post the code to reproduce on the 🧵

Hey this is kind of a digression, related to the topic of performance and baseline profiles. And this is probably a naive question, but I was wondering: why not compiling the whole app, ahead of time? Instead of just the "hot spots"? Which need to be collected beforehand and then packaged etc. What am I missing?