Am I the only that gets a questionably looking button by default with Wear Compose? The padding is m...

# compose-wear

[louiscad]

Am I the only that gets a questionably looking button by default with Wear Compose?
The padding is missing.

I'm quite confused at why this would be the default and what is the correct thing to do since on Material 3 for phones, it just looks correct with the right inner padding applied.

[yschimke]

Are you using Button? For this it should be a Chip.

[louiscad]

Yes I am using Button. Why should it be a Chip?
Button seems the most intuitive naming, no?

[yschimke]

It has a specific meaning and design with Wear Material https://developer.android.com/training/wearables/compose/buttons

[yschimke]

Chip is what you want https://developer.android.com/training/wearables/compose/chips

[louiscad]

Shouldn't this be named IconButton, and have Button correspond to a text button, like on phones?

[louiscad]

Or maybe named CircleButton since it seems to be designed for that, despite the fact that the resulting layout doesn't render as such as you can see in my screenshot

[yschimke]

I see your point. But I'm not sure who you should have this debate with. But it's not me 🙂

[yschimke]

cc @Kseniia Shumelchyk some feedback on naming. FYI only.

[louiscad]

I'm even less sure… but I'd love to know!

[louiscad]

Button `Chip`/`CompactChip` look much nicer BTW, thank you!

[John Nichol]

I think @yschimke has covered the key things here. There are historic reasons in our original UX specs for Wear OS 3 that resulted in us using Button for small circular buttons and Chip for non-circular longer buttons. We discussed this at length late in the 1.0.0 release cycle. We had not seen much confusion over this issue, probably because most of our samples and codelabs use Chip everywhere - as a result we decided to leave it as it was. However I accept it has caused confusion for you and so therefore there will be others. We are starting to plan for our Material3 compose library which will give us a chance to rethink our naming strategy.

[florent]

It would be nice to have a page like this for wear os with a list of components and the implementation https://developer.android.com/reference/kotlin/androidx/compose/material3/package-summary

[louiscad]

Agreed. It was very helpful to me as I'm making the companion app. Same for Wear OS would make it a breeze to learn about the components.

[John Nichol]

@Danilo Di Cuia do we have this in our public docs anywhere?