Mac died after almost 20 years. Got a new Apple MBP M1Pro. Super happy with the SwiftUI iWatch dev but can not find a WearOS image? Super confused ... how are people testing WearOS on M1? We can use https://developer.samsung.com/remote-test-lab or buy a device but it would be nice to run the emulator ... no? HELP 🙏🏽

Compose for Wear OS Alpha13 shipped yesterday. Includes some improvements to navigation and also fixes to allow building of release configs which will allow folks to test their applications minified and with resources shrunk to get a better view on performance.

There is any way to create watchfaces with Compose?

Looks like Jetpack Compose

1.1.0-rc02

(well, Compose Compiler part anyway) works with Kotlin 1.6.10....should there be wear compose version right now that also works with that? https://kotlinlang.slack.com/archives/CJLTWPH7S/p1639683988274300

If we say we are doing Declarative Programming ... shouldn't the code be the same for both round and square but the Composable does the correct layout for the device? So we should not need this

if

statement. These should both just be Row and each WearOS device doing the correct rendering ...

if (LocalConfiguration.current.isScreenRound) {
    CurvedRow(
 } else {
    Row(

This does not feel like Declarative to me ??? 🤷🏽

What is the expectation for slots in components like ToggleChip? I didn't notice appIcon, so I put the icon inside the label to start with. Because label is placed inside of a Column, with secondaryColumn, I surrounded it with a row. But it seems like the Column parent is leaking an implementation detail? How do Compose mobile components handle this? Should it be a parent Box? Should it fail if the label @Composable has more than one direct child?

Can you use let for this? See https://discuss.kotlinlang.org/t/let-vs-if-not-null/3542 mediaItem.mediaMetadata.artworkUri?.let { it -> ... }

Need a little help ... Android Architectural Components works on WearOS? Trying to use Hilt, ViewModel, Repo, Room DAO with Koltin Flow and Compose (w/ Navigation). This should all work? Right?

Who has customized wheel picker to use compose? thank you!

Hi, I found two errors while developing WearOS with jetpack compose. 1. Textfield - I think it will be fixed soon. 2. Screen is locked with ViewPager2 - I report it in issueTracker... • https://issuetracker.google.com/issues/209359388 I wonder when the bugs will be fixed. And can i ask this question here?

App with wear os compose 1.0.0 alpha13 deployed on wear emulator crashes wenn I open the Layout Inspector in AS. Is it a known issue? With Layout Inspector closed, the App is just fine. Is any workaround to use Layout Inspector with wear os compose?

I want to make the time text in scaffold disappear, when the ScalingLazyColumn scrolled up. Is there a better approach as check the first element in

layoutInfo.visibleItemsInfo

and its

offset

?

...
        val listState = rememberScalingLazyListState()        
        Scaffold(
            timeText = {
                val itemInfoList = listState.layoutInfo.visibleItemsInfo
                // the first element is scrolled up more than 15dp, deactivate the Time Text
                if (itemInfoList.isNotEmpty()
                    && itemInfoList[0].index == 0 // the first visible index is the first element
                    && itemInfoList[0].offset >= -15 // the first element is scrolled up less than 15dp
                ) {
                    // show time text
                    TimeText()
                }
            },

The StarWars sample form @John O'Reilly is a nice KMM and GraphQL (apollo) example, including for Wear. https://github.com/joreilly/StarWars

I am running into an issue where my compose wear app crashes with a NullPointerException when navigating between screens using the wear compose navigation library. Found an already reported issue here: https://issuetracker.google.com/issues/206677462. Could someone please look into this? This is currently blocking me from using compose on Wear OS.

About to release my first Jetpack Compose/ WearOS3 app! This was my first introduction into Jetpack Compose and WearOS3 (there's a Tile that goes with the app). I've made apps and watch faces back when I still had the original moto 360, and it's awesome how far the wear ecosystem has come (still has a long way to go, but on the right track!) This is a complete standalone app for interacting with the Philips Hue ecosystem. Open to any thoughts on design, features, etc. Also if anyone has Philips Hue and is interested in beta testing, let me know!

For CurvedText, if drawing at the bottom, is there a way to flip it so it's not upside down?

Bumping up

Compose for Wear OS Alpha 14 is now available - release notes here. Includes major changes to ScalingLazyColumn to support a) anchoring list items to the centre of the view port, b) changing the list item offsets to be w.r.t. that viewport center, and c) adding methods to scrollTo and animatedScrollTo items in the list. Scrolling to list items will bring them to the center of the view port.

In Compose for Wear OS Alpha 14 now, the

offset

of

ScalingLazyListItemInfo

are either related aligned to the centre of the viewport or to the top edge either from center or edge of a list item with anchorType

ScalingLazyListAnchorType.ItemCenter

or

ItemStart

while initialising the ScalingLazyColumn, the option of offset to its initial position of Alpha 13 are now gone. How can I detect that the ScalingLazyColumn has been scrolled up e.g. 15dp?

Hello! Is there equivalent for CircularProgressLayout available in Compose for Wear OS? Thank you!

I don't actually know who deserves credit, but the Wear Specific previews in Android Studio Canary are pretty great. PR for sample project https://github.com/android/wear-os-samples/pull/206

Who has done similar work on paging navigation? I can't find the code on the document. thank you!

When implementing a standalone application, is there any way to authenticate the user while using Compose?

Related to the paging navigation discussion above, one glitch I've noticed is that it seems easy to accidentally swipe to dismiss the main screen with paging instead of switching left. Is it easy to disable that? I know I'm using SwipeDismissableNavHost, but that seems to have a lot of logic I suspect I otherwise need. cc @Steve Bower [G]

Hi - could you paste some compose code to illustrate the problem? It sounds like there must be something like Modifier.padding(<some non-zero value>) in your composition, because otherwise compose does draw up to the edge.

I want to re execute some code for view rendering in the composable method. How do I implement it? Do you have a general idea. thank you！

Compose for Wear OS Alpha15 has been released. A few additions and changes - one in particular to draw your attention to is that we have added what we call `autoCentering`which will automatically provide space before the first and after the last items in your

ScalingLazyColumn

removing the need to provide top/bottom/vertical content padding - so look to update your padding as part of upgrading.

https://android-developers.googleblog.com/2022/01/announcing-glance-tiles-for-wear-os.html?m=1 Is this relevant for this channel?!

Hey, I have started rolling out a new version of my Wear app using Compose Wear to some beta testers. Some users are getting the following crash:

Fatal Exception: java.lang.IllegalArgumentException: No WearNavigation.Destination has been added to the WearNavigator in this NavGraph. For convenience, build NavGraph using androidx.wear.compose.navigation.composable.
       at androidx.wear.compose.navigation.SwipeDismissableNavHostKt.SwipeDismissableNavHost(SwipeDismissableNavHostKt.java:166)
       at androidx.wear.compose.navigation.SwipeDismissableNavHostKt.SwipeDismissableNavHost(SwipeDismissableNavHostKt.java:87)
       ... (redacted)

Note that it works great for most users, so far this crash is only affecting a few users. I am not able to reproduce it myself. I am creating my nav host like this:

SwipeDismissableNavHost(
    navController = navController,
    startDestination = "mydestname"
) {
    // Note that composable is from androidx.wear.compose.navigation package.
    composable("mydestname") {
        ...
    }
    ... more composables
}

The crash seems unexpected to me as there are always destinations added, so I suspect this is a bug. This is using androidx.wear.compose:* snapshot 8104636 and androidx.navigation:* 2.4.0-rc01. Any suggestions?