Testing the tile on Pixel watch2 and it seems the ...
# compose-wear
t
Testing the tile on Pixel watch2 and it seems the content size does not adapt to the smaller size. The layout is the golden from the sample with
Copy code
PrimaryLayout.Builder(deviceParameters)
    .setResponsiveContentInsetEnabled(true)
Is there some more docs about how to build better responsive Tile?
y
There are some doc updates coming (I shouldn't promise things for others). But that should address a lot of the UX guidance, and also the code to achieve it.
t
Hum ok thanks. So I guess no ETA ? Do you know if the tiles are part of Play Store review team?
y
In this case, I would suggest only showing the title when the DP is > 225. Alternatively keep the title, and show 1 or 2 chips depending on the size.
Do you use the Tiles Previews?
t
Not yet, not enough hours so I built first then improve over time. Is there a way in the manifest to tell the tile is only for large screen? I guess I can get the sizes in the deviceparams and degrade if needed.
y
Not that I know of
image.png
cc @Mohammad Saboorian
t
Thanks a lot for the solution, the chip is not cut so I guess this will pass the review.
Finally quickly rebuilt the chip to match the wanted design and be adaptive, the non large chip still have a bigger height than a compact chip so I guess it's OK from accessibility POV.
The main pain with protolayout is all the builders making it quite hard to find when there's a short version like `ColorBuilders.argb`or
DimensionBuilders.sp
versus the ultra verbose full builder.
y
Looks great
I think a lot of people build their own slightly domain focused kotlin dsl
t
Thanks, removed the compact chip icon and tweaked the padding. For the DSL most apps will have max 1 tile, not sure it's worth it for every devs to rebuild a complete design system for that. Let's hope the M3 proto will allow some liberty to simplify things.