IssueTracker

Hey, thanks for the feedback! There's a couple of things we're working on at the moment to try and help this out, both to reduce the amount of code required to implement common designs, and to provide a better Kotlin API.

We've recently released the first alpha of glance-wear-tiles, which allows you to build Wear Tiles in a Jetpack Compose-like API (as you alluded to in your message :) ). We're still in the early days, but it'd be great to get some initial feedback there.

We're also building up a Material component library for Tiles (androidx.wear.tiles:tiles-material), and just released the first alpha version yesterday. It's still using Builders throughout, but it aims to provide consistent Wear Material components for Tiles, so should also reduce some of the code needed to build up Tiles.

It's still very early days on both projects, but it'd be great to get initial feedback on these projects too!

Awesome! I'm excited to try it out :) thanks for your work!

So Glance will also work for normal appwidgets? That's even more awesome!

In general, yes. That said there's a few caveats:

• Using any of the target-specific Composables (e.g. androidx.glance.wear.tiles.curved.CurvedRow) will not work on other targets (your app will compile still, but it won't render).
• If you're just using the base set (e.g. the ones in androidx.glance), then the same code will work on both Tiles and Appwidgets, but you'll still need to test on both and tweak the layout so it renders well on both targets.

Thanks for the feedback, Jolan! Please try out Tiles Material (there's a new codelab out, you'll have to use the 1.1.0 rc) and open a new ticket to give us feedback about the API.

The underlying structure is the same as the OG Jetpack Tiles API, but it should be a lot easier to build Material-friendly layouts with the new one, and hopefully a lot less boilerplate.

(Glance: Tiles is still in development but it's still in alpha.)

Will close this ticket off. (I chose "fixed (verified)" as it's a feedback issue and the other statuses apply less.)

What's a way (if any) to make this issue noticed and fixed?

The inability to have a settings screen in your Wear app: not a big deal?

My app is now rejected from the Play Store because of this issue (yes, your screens must look good on round screens to be accepted on the Play Store).

That is unfortunately not a solution for me since I'm already using AndroidX fragments in my codebase, and you can't mix them.

Hi,

Title not showing and margin between widget and text being too big are not a bug since this is intended behaviour for the phone.

In order to better understand the need for this, could you please give us more details on the actual use case where this doesn't look good and is there a UX design for it?

Cheers