Any reason for M3 AlertDialog to be using ScalingL...

# compose-wear

[Tolriq]

Any reason for M3 AlertDialog to be using ScalingLazyColumn and not TLC ? This leads to very different animations for the items.

[yschimke]

Some inflight CLs for that https://android-review.googlesource.com/c/platform/frameworks/support/+/3753588

[Tolriq]

Thanks, seems as always I'm too ahead of times each time I decide to update the Wear app 🙂

[yschimke]

It's hard, because early adopters shape the API. And I wouldn't want to build on the first material library now, it's not actively maintained. So many improvements by steve and rest of the team went into m3

[Tolriq]

My previous version was nearly full custom to be normal M3 😞 Had to duplicate a ton of stuff from M3 and horologist and write full custom tiles stuff. This times it went a lot smoother so thanks to the team 🙂 Just missing the shapes and wavy indicators, but I'll probably skip them for now as too lazy.

[yschimke]

What are you missing for shapes. You should be able to apply graphics shapes even morphs as container shapes.

[yschimke]

And wavy indicator, I guess you'd have to reuse mobile material 3?

[Tolriq]

I opened a quick issue as asked by Steve https://issuetracker.google.com/issues/451733088

[Tolriq]

Since the themes and everything are not compatible, it needs copy pasta all over to reuse, and then maintain;

[Tolriq]

Would be nice to copy the media session stuff specially since it's in the demo screens of how to write nice M3 expressive media player, but I'll wait for the ports.

[yschimke]

Those components are in horologist. They might be slightly behind the apps.

[yschimke]

https://github.com/google/horologist/blob/main/media%2Fui-material3%2Fsrc%2Fmain%2Fjava%2Fcom%2Fgoogle%2Fandroid%2Fhorologist%2Fmedia%2Fui%2Fmaterial3%2Fcomponents%2Fanimated%2FRotatingWavyProgressIndicator.kt

[Tolriq]

Lol I completely missed that 🙂 Well thanks for adding more work 😛

[Tolriq]

Thanks for the link.

[yschimke]

I think jetcaster got bumped to use them also

[stevebower]

Yeah, as Yuri pointed out, we are working on providing TLC-scope overloads of AlertDialog in our 1.6 release.

[Tolriq]

@yschimke Seems Jetcaster is not updated after all. Is there some pending PR or doc about what should be done to generate the player colorscheme and use with AnimatedColorScheme from the paintable ?

[yschimke]

Oops sorry thought it was

[yschimke]

I'll take a look tomorrow

[Tolriq]

I looked a little everywhere and could not find anything or details. I think I'll do it manually as in the main app for now. Do you know if there's some official details about preferred colors to choose from the image to ensure contrasts ?

[Tolriq]

Not so bad for a first try.

Screen_recording_20251022_185606.webm

[yschimke]

That looks great

[yschimke]

Shit, "tomorrow" is now tomorrow

[Tolriq]

:) No problem I get it to work and it's using a port of the official theme color stuff. Would just be nice to know the official palette style to use. Currently using TonalSpot with 2025 specs.

[yschimke]

No plans to make the colour scheme generation public

[yschimke]

Wear compose gets the theme ones from theme colour resources. And the Media Controls logic is inside the media APK.

[Tolriq]

Hum ok that's strange the official code is public https://github.com/material-foundation/material-color-utilities pretty sure they use that too, would just need a guidance on the palette type expected. Anyway so far the one I chose and implemented seems to work well. I guess I'll go with that even if that's one more thing we can't ensure consistency.

[chiara chiappini]

regarding Jetcaster: https://github.com/android/compose-samples/blob/main/Jetcaster/wear/src/main/java/com/example/jetcaster/WearApp.kt is using the horologist material 3 screens for media. Can you share what is missing?

[chiara chiappini]

(perhaps not updated to the very latest API versions but it's been updated for material 3)

[Tolriq]

It's not using the animated ones nor is using the artwork background / dynamic colors as per the wear m3 expressive guides.

[chiara chiappini]

Yeah, it's accurate that these 2 features are not available on that sample.

[chiara chiappini]

Is anything else missing that you noticed?

[Tolriq]

No that's the one that needs details from Google to implement as per the specs. There's videos, docs and everything. There's even https://developer.android.com/design/ui/wear/guides/patterns/media/color that says The system creates a theme for your app's media controls by sourcing a seed color from the current media entity's artwork. But it only does that for the media session controls, this is not accessible from apps. The docs also says "Align UI patterns and avoid creating new UIs for common interactions." with the

https://developer.android.com/static/wear/images/design/media-music.png▾

image. There's ultra detailed specs like https://developer.android.com/design/ui/wear/guides/patterns/media/controls but all the color stuff and background is ommited.

[yschimke]

Yep. The underlying libraries are basically the same. But then tuned for the colours of the palette. A lot of lookup tables and coefficients you would need

[Tolriq]

So they don't use any of the official M3 palettes that that library offers and are the official 2025 m3 expressive colors? All the coefficient and tables are already there, all the stuff to extract and quantize colors from images too. That's strange that they invented something else. Maybe you could still find someone to say that from the official stuff it's better to use TonalSpot or Vibrant or another from that official palette guide. I'm too dumb with colors to decide what's best and what looks the most like the media session controller.

[yschimke]

I'll confirm if they match any tomorrow

[Tolriq]

Thanks, don't waste too much time on this. We don't necessarily need a perfect match but some pointers on what we should do with the tools that we have at disposition to point toward the target they show.