What are the main challenges to make compose multi platform? I understand that it is not a priority for Google now but how far does the design help and can people from the outside contribute for support?

Not speaking for Google here but it looks like at this stage community can really help by trying it out and giving feedback on the current design of compose.

@miha-x64 Do you really want Android Jetpack to compete with e.g. Flutter on crossplatform field? I think that new UI framework must be robust. Do one thing and do it well

Flutter has no support for modern languages, e. g. Kotlin and/or Rust. There's nothing to compete with.

It is the product of Google, after all. Same as Android Jetpack. I think, that this may cause unneeded conflict of interests

Google causes conflicts of interests every day, creating and killing new messengers, frameworks, operating sustems etc.

Compose will tremendously ease up UI development on Android. It doesn't have to be multiplatform at all. It's just that right now the community could help steer the Compose project so that at least the DSL is platform independant and one could e.g. write an iOS implementation for showing the views.

or IoT impl, think of the Pi’s, the Pi’s!

Raspberry Pi is inefficient. Consumes too much power for what it can do, and consequently can't scale, in addition to the fact that it was not designed for IoT but for education.

🤔 ok, not really the point I was making. Any embedded platform

+1 for having a single DSL that could work across Android and iOS (maybe even in the browser, but the mobile use-case is probably the strongest)