Maybe someone here will have more info on <https:/...

# compose-desktop

[eygraber]

Maybe someone here will have more info on https://kotlinlang.slack.com/archives/CJLTWPH7S/p1646626860089129 (didn't get any traction in #compose)

[Grégory Lureau]

Jetbrains Compose is for Desktop
Google Compose is for Android
You should pick the Android one.

[Grégory Lureau]

You can look on github samples, there are a lot of them with full configurations (ex)

[Landry Norris]

I can’t speak for whether Android Compose works in an Android Source Set for KMM (I don’t see why it wouldn’t), but I have been using Jetbrains Compose in the androidMain folder for a while with no problems (I have moved to creating a composeMain source set to take advantage of desktop and maybe iOS one day, had no issues with this structure so far).

[Grégory Lureau]

I thought about using Android stuff like navigation that are only exposed in Google Compose and not in Jetbrains one, given the original post was referring Android source set. A bit surprised that Jetbrains one can run on Android but then I presume it's a subset of what Google did right?

[Landry Norris]

Jetbrains Compose just points to the Android artifacts on Android as far as I can tell. I noticed that decompose dropped the separate android and jetbrains compose interop modules, saying something along the lines of compatibility with jetbrains compose implies compatibility with android compose.

[eygraber]

Using Jetbrains compose is working fine, but I'd prefer to use Jetpack compose (at least until the cross versioning is more stable).