Anyone else feel it's a little weird that Google h...

# multiplatform

[Bam]

Anyone else feel it's a little weird that Google has introduced Material 3 Expressive only for Android, while at the same time attempting to make Material 3 universally accessible through built-in Jetpack Compose across all supported KMP targets, especially iOS with it becoming stable only recently?
Is the following statement now correct: "Using Jetpack Compose in a KMP project can now give you Material 3 on all supported targets, including iOS! Yay! But Material 3 Expressive can only work on Android, so you cannot use it for Common UI shared across targets."? 🤷🏻‍♂️

[SaurabhS]

I don't think Google releases multiplatform artifacts for Material 3. Jetbrains does that.
Some Material 3 expressive components were already available on desktop in the early CMP 1.8 alphas. They'll probably be available again in 1.9 alphas.

[Bam]

I get that Google does not themselves release the Material 3 work, but it just seems weird for them to all of a sudden do all this new stuff for Android only, and have those that work on the Multiplatform Material 3 artifacts play catchup.
Why not just work in a way that does not create this initial divergence?

[zsmb]

The above reply is correct, Google ships most libraries only for Jetpack Compose, and these libraries are adapted and published for multiplatform by JetBrains.

Material 3 Expressive is basically a new version of the Material 3 library - we'll catch up with it when we have the resources to do so, there's always lots of merging work like this across Compose libraries (there's navigation, lifecycle, and others too).

[Bam]

Understood. Thank you for taking the time to clarify. 🙏🏼
I am sure the features in both libraries will converge soon enough.
Looking forward to trying out all the new stuff.

[Daniel Dello]

On a quick chat with a Google Dev working on this expressive framework during an event he mentioned the library is still marked as experimental for Compose 1.8 and will probably be so for 1.9 as well, so maybe we should wait a little longer before fully jumping on board. They apparently used mostly common frameworks that should be easy to port to KMP, but their focus is on Android.