Question, how come

import androidx.compose.foundation

ui

etc work in compose desktop? In my android project I tried to use those dependencies in a pure

kotlin

(jvm) module (just some extensions, no @Composable stuff), and gradle complained about the module not applying `kotlin-android`so I figured those have an android dependency? Or did I mess something up?

Compose for Desktop has its own artifacts that can be used in pure JVM modules.

but how? when I click into say

MaterialTheme

class, its exactly the same is it just a copy? they take all of the android compose sources, and strip the android stuff, and publish?

Basically that, and delegate to Google version for Android.

Tldr; if it were interfaces then I'd get it, they just provide desktop impl, but its whole concrete sources, so it must be a copy

Sounds like you need to learn some basics of Kotlin multiplatform.

that might be true, but looking at the dependency graph I'd expect there to be some androidx dependency, where the jetbrain dependecy provides the `actual`s but yea, I never actually built stuff with kmm

if you apply the org.jetbrains.compose gradle plugin, it'll give you a shortcut for the proper dependencies (e.g.

dependencies { implementation(compose.foundation) }

), substituting them as appropriate for Android

Yes but my question now is, say

MaterialTheme.kt

, is in both the jetbrains and in androidx package, is it 1) pulled in via som dependency (not visible in the graph 2) or is it a "copy paste"