Compose doesn’t seem to be really tight to Android. I might be wrong, but we could probably “just” change a rendering function to make it able to draw on a different canvas. I perfectly understand it’s certainly not the priority but it’s cool to think that in the future it might be possible.

Are these green 🍎 reactions a reference to the company, Apple?

I was thinking the same thing, compose is awesome and if we could write one and work in iOS too, will be great

They don't have plans to make it multiplatform, because that's what flutter is for. Before they announced it I was planning to convert Flutter into kotlin. Flukker. But then they announce Compose which should have been called Kompose but minor details

I believe some guy from Google said it would be Klutter

besides, if there is only 1 thing google is good at, it's having 10 solutions for the same problem 😂 case in point: messaging

In last year @Gil Goldzweig I was thinking in use the Flutter Engine with Kotlin Native and write a Flutter in Kotlin because I really love the kotlin language, but I never found a away to even try that, and Flutter Engine is written in C++ and it makes things harder for me. Backing to compose, the guys from compose don't need to think about it and don't need to do nothing about it too, but will be great if they build the compose to this be possible in the future with some project from the Kotlin community, porting to iOS(I don't know if the guys is thinking about it, because they have so much work to do in compose). (sorry my bad english :S)

@SrSouza Your english is fine, don't worry about it. I don't think they want to make it compatible with IOS but I think the syntax is close enough to the new SwiftUI that it's going to be easy to make the conversion

(somewhere in this channel, they mentioned that cross platform is do-able, but not in any priority right now) and for translation between compose <-> swiftUi, it will probably comes down to "all the little differences between the 2 platform, and it's really really hard to do perfect translation" all over again (which is why i assume flutter scrap everything instead of doing what RN does)

It’s not because Google already have Flutter, that this project cannot be multi-platform. Also, from what I understand, Compose it’s only for building UI, there is nothing really attached to the android environment, where Flutter has a lot more. It’s like comparing React and Angular, they are not really the same. Or React-Native (use native components) and Flutter (use a method similar to Compose). Or I am totally wrong 😮