Hi folks, I do have a library for Compose Multiplatform that I want to support both Android (Jetpack...

# compose-desktop

[SrSouza]

Hi folks, I do have a library for Compose Multiplatform that I want to support both Android (Jetpack Compose) and Multiplatform (Jetbrains Compose). I'm having doubt about using the Jetbrains Compose plugin to for publishing for both type of projects, I read in this channel that Jetbrains Compose 1.0 is not using Google's Compose Stable release (1.0) instead is using the Beta version from 1.1. I want to know if anyone call tell if publishing for both using the Jetbrains plugin could have issues for people that is using Google Compose stable version (1.0).

[Big Chungus]

I'd just hold off until jb compose supports kotlin 1.6 and then publish the lib with jb compose. For now, there are some issues preventing the upgrade (thus jb compose not using google compose 1.0)

[Alexander Kurasov[JB]]

I would separate two topics: the JC version that CfD references and the Kotlin version that CfD 1.0 uses.

From API perspective CfD 1.0 is much close to JC 1.1-beta that it references, than to JC 1.0. However as Compose is backward-compatible, I wouldn’t expect much issues due to it.

From Kotlin perspective - there is a plan to issue Compose Multiplatform 1.0.1 working with 1.6.10 and referencing latest available JC at that moment. However, most probably there will be no JC 1.1 at that moment.

From the API perspective, if you want to be on the safest side, you should wait JC 1.1 and Compose Multiplatform stable release that will reference it.