Not exactly compose related, but I noticed all apps when I open show the icon on black background while loading as splash but mine is just a black screen until the app loads. How do I make this splash screen?

Compose for Wear OS 1.0.0-rc01 has been released. We expect this to be the only release candidate with the next release being the 1.0.0 final. The release includes a few UX updates to match the latest UX guidance and small enhancement to enable

ScalingLazyColumn

to be visible in Android Studio Previews.

Is it possible to add elevation to wear compose chip and also make it outline style? Or is it desired for the watch design guidance to not elevate chip or make it outline? I would like to make this 👇 elvated 8.dp and outline style.

I have a quick question to the

WearNavScaffold

of horologist. I used a

scalingLazyColumnComposable

to show a menu and default time text. Wenn I swipe back to the menu screen, the time text is gone. Is it desired behaviour? My navi graph code

What composable could I use to generate a screen with multiple buttons and text element? Is it scaffold? Maybe someone knows where to find a code example for something similar?

I need to use

rememberRipple()

in a shared module. Is it OK to bring in material as

implementation

(not

api

) even though the module is eventually consumed by both phone & wear variants that make use of material/material-wear? Docs advice against mixing these up, but afaik thats just to ensure that you dont make use of the wrong

MaterialTheme

(etc); material-wear itself depends on material?

Are there clear conventions on where to put a Background on Composables? Or where assumptions about MaterialTheme.colors.background are applied. I just did a deep dive investigating an issue reported for the Media UI and think I've come to the conclusion that user code should almost never set a background, unless it's specific to a Screen such as Artwork.

I was taking a look into the Tile documentation and it says that you can add some time for refreshing the tile using the

setFreshnessIntervalMillis

when overriding

onTileRequest

. I'm using the Horologist's

CoroutinesTileService

where

onTileRequest

is final so I can't change when it should refresh. Is there some option for it?

Just to be sure: Compose doesn't support text hyphenation yet, right?

The example discussed previously of using Compose DrawScope to share elements between Canvas and Tiles is now available in the Horologist library. API is still very experimental, mainly around pixels/dp params which I don't think is right yet. But let's you draw the same weekly goals chart to your app and tile. Design first in compose, use compose previews to edit the chart, and then reuse in a Tile.

Compose for Wear OS 1.0.0-rc02 has been released along side Core Compose 1.2.0-rc02. There are a few small UX tweaks for gradients backgrounds on Chips and Cards. The 1.0.0 final version of Compose for Wear OS will be released along with Core Compose 1.2.0 final in the coming weeks.

is there anything similar to

animateItemPlacement()

for

ScalingLazyColumn

?

In the same vein, any plans to support sticky headers? I know they are still experimental in LazyColumn but I'm finding myself needing them for my little Wear app 😊 (will use LazyColumn for now)

Compose for Wear OS 1.1.0-alpha01 has been released with accessibility improvements for Pickers. Due to a break for the US 4th July weekend the next releases are scheduled for 29th July

Not sure if anyone else is doing similar, but I've found it helpful to use paparazzi to compare our stateless composables against Figma designs

Interesting question on Stack Overflow https://stackoverflow.com/questions/72833107/jetpack-compose-wear-os-scroll-to-top-onresume Jetpack Compose Wear OS Scroll to top onResume?

[Solved] Will there be a horologist modifier to detect bezel event for ScalingLazyColumn? The

scrollableColumn

modifier doesn’t seem to register the rotation of GW4 bezel. Is this still the way to do it with

onRotaryScrollEvent

modifier (https://stackoverflow.com/questions/70060650/how-to-implement-positionindicator-for-bezel-galaxy-watch-4-classic-wear-os-3) ?

Is there any guidance for how to do deeplinks from a Complication to a Wear Navigation app?

I used to get

"cannot access file, it is used by another process"

errors after adopting compose for my phone app; I saw that IntelliJ addressed it in one of their latter releases, and after it got merged into Android Studio I havent ran into it again. Unfortunately, the same thing seems to repeat itself now that Im actively working on a wear specific app. Has anyone else ran into this? Any insights?

Im considering creating a custom Text composable that I can reuse across phone/wear variants of my app. Im mostly worried about

TextStyle

provided through

LocalTextStyle

, which I wouldnt have any access to. At the same time, I have my own design system (which leans on material); components with text all make use of my custom Text composable as well (and provide the appropiate style). The material/material-wear text composables look very similar to me, is there anything else I should keep in mind before doing this?

Q: Isn't there a simple way to have a

ScalingLazyColumn

with a

TimeText

as the first item, so it scrolls with the rest of the contents? (Like the system settings). The samples I can find seem to make it fade away in complicated ways 🙂 And if I naively put a TimeText as the first item in my list, it takes the whole screen height 🤔

Another question: the recommended way to have toggles in a settings-like screen is to use

ToggleChip

with

ToggleChipDefaults.switchIcon

, correct? Is there a way to animate the toggle switch?

Hey I noticed a small animation glitch when showing a dialog. I think it's a vignette appearing for a second at the begin and end of the appear/disappearing animation of the dialog

quick one, I saw @yschimke’s reply to a StackOverflow question related to launching the Gboard activity on a compose wear app. I want to find out whether it is possible to specify to Gboard to open the keyboard directly (as the first screen that shows up) instead of presenting the user with an option to select between audio and text input. For more context, my app already provides a custom audio input alternative for the user, because of this, the extra audio input support provided by Gboard looks a bit redundant.

Hello, is there a way to get the chin height in a composable?

A quick question unrelated to compose, but regarding migration to androidx. Is there a guidance of how to migrate

com.google.android.support:wearable

to the

androidx.wear

libs? There is a mapping for the

android.support.wear

lib (https://developer.android.com/jetpack/androidx/migrate/class-mappings), but I haven’t found one for

com.google.android.support:wearable

sofar, which contains Watchface, Complication and so on, the kotlin one might be https://developer.android.com/jetpack/androidx/releases/wear-watchface, and it feels almost impossible to just switch the libs, but more like to rewrite everything new. I would really appreciate any hints of how to do that gradually, instead of a big bang.

The Compose for Wear OS team is pleased to announce that version 1.0.0 final is released. The release includes a small number of bug fixes from the RC02 but the API is as per the Beta01. Release notes can be found here. Thanks to all of the developers who provided feedback, raised bugs, asked questions to help us reach this milestone.

This plugin is quite handy if you are testing with paparazzi https://plugins.jetbrains.com/plugin/12691-image-diff

I feel optimistically close to having Wear specific support for Compose in Paparazzi. https://github.com/cashapp/paparazzi/pull/411

Is the ScalizingLazyListState() and ScalingLazyColumn autoCentering conflict still present in wear compose-material:1.0.0? The following code doesn’t work, which shows only a dark screen at the beginning.

val state: ScalingLazyListState = rememberScalingLazyListState()
Scaffold (
     vignette = { Vignette(vignettePosition = VignettePosition.TopAndBottom) },
     positionIndicator = { PositionIndicator(scalingLazyListState = state) }
) {
     ScalingLazyColumn (
         modifier = Modifier.fillMaxSize(),
         verticalArrangement = Arrangement.Center,
         state = state,
         anchorType = ScalingLazyListAnchorType.ItemCenter,
     ) {...

After I set the ScalingLazyListState(), and autoCentering both to (0, 0), the first element is shown correctly.

val state: ScalingLazyListState = rememberScalingLazyListState(
            initialCenterItemIndex = 0,
            initialCenterItemScrollOffset = 0
)
Scaffold (
     vignette = { Vignette(vignettePosition = VignettePosition.TopAndBottom) },
     positionIndicator = { PositionIndicator(scalingLazyListState = state) }
) {
     ScalingLazyColumn (
         modifier = Modifier.fillMaxSize(),
         verticalArrangement = Arrangement.Center,
         state = state,
         anchorType = ScalingLazyListAnchorType.ItemCenter,
         autoCentering = AutoCenteringParams(itemIndex = 0, itemOffset = 0)
     ) {...

And set to (1, 0) as the both defaults are, doesn’t work. (0, 0) seems to be the only working combi. I think this issue was also present in horologist (https://github.com/google/horologist/issues/245). Any thoughts on this are appreciated. Update: It is worth to mention that my items are two full screen elements. After I scrolled the screen, the code behaved like I had set (0, 0).

item {
   Box(modifier = Modifier.fillMaxSize(), contentAlignment = Alignment.Center) {
      Text(text = "Hello World!")
   }
}