I am curious how complex it is to create an iOS specific MaterialTheme instance such that we can have a more native looking UI on each platform...

iOS design system is not Material at all… It’s not just colors, but also other design elements, behaviors, animations, effects, etc.

I understand that. But the sample code in shared is like so:

@OptIn(ExperimentalResourceApi::class)
@Composable
fun App() {
    MaterialTheme {

Are you suggesting that this MaterialTheme is already adjusted to look more like iOS when on iOS?

I don’t know for sure, but I guess it is not. Same theme as on Android, Desktop or any other platform, same components and their behaviors. With M3 you can tune more aspects, but it’s still Material.

@tylerwilson I don't think Material will be eventually adjusted to match iOS-style(called Cupertino), in Flutter the user has the possibility to use

OS specific

widgets, like this, my guess will be that maybe in the future we could have something similar in Compose

For now I would be happy to be able to do something like expect/actual CustomTheme which would let me adjust colors, type, shapes between the two, but use the same composables in common. thanks.

iOS design system is not Material at all

Yup. I wonder why people want to use Material Design for iOS. I suppose the same people use the Roboto font in their iOS apps. 😉