Hello, it has been a while since Wear Compose Mate...

# compose-wear

[louiscad]

Hello, it has been a while since Wear Compose Material 3 first 1.0.0 alpha 01 release.
Now, more than a year after, we've seen 22 more alphas, and still not even a beta in sight.

Why not use @RequiresOptIn for the APIs that are still much WIP, and commit to a beta then "stable" release, so we can use the stable components, and know which ones could change and whether we want to use them anyway?

I'm about to do some UI for a Wear OS app, and I don't know how risky it is to use Material 3 over the apparently stable Material (2) artifacts. I'm lost!

[Tolriq]

There's still too many missing components to do only M3 for now. A few are in the CL list, but still no dialogs for example that would require rewriting a complete one by maybe copying horologist.

[Tolriq]

I'm currently using both in a new app with dual theme and careful imports you can get something working as during the normal compose M2 to M3 transition.

[Tolriq]

But lot's of details to check everywhere 🙂

[florent]

I would not use material 3 yet as they don't have all the components and the migration would be easier as you mostly only have to change import name and the color scheme.

[Tolriq]

No they change many paradigms like no more chips it's buttons and so on. The migration won't be just change imports and scheme (And the scheme also change a lot with the new surfaces 13 Colors to 28 Colors)