Does <this> mean that with 1.9 Jetpack Compose will be the sole implementation of Compose across all...

# compose

[eygraber]

Does this mean that with 1.9 Jetpack Compose will be the sole implementation of Compose across all targets, with Desktop, Web, etc... specific code being provided by Jetbrains?

[ephemient]

that's not how I read it. androidx.lifecycle:lifecycle-{common,runtime,viewmodel} are KMP already, they've extended the set of available platforms. andoidx.lifecycle:lifecycle-{runtime,viewmodel}-compose are also KMP, but do not have the new targets yet, since androidx.compose-*:* don't have those targets either; that may be coming in Compose 1.9

[eygraber]

Right, I meant is this a precursor to supporting that.

[ephemient]

androidx.compose* supporting them is a prerequisite to androidx.lifecycle:*-compose supporting them

[ephemient]

not the other way around, if that's what you meant?

[eygraber]

I think one of the bigger roadblocks to supporting all targets in the past was adopting Google's androidx repo to including js and wasmJs, but it looks like that isn't an issue anymore.

[Ian Lake]

Compose Runtime is what is adding more KMP targets in Compose 1.9

[eygraber]

Can you comment on the rest of the artifacts 😅

[Ian Lake]

They are not getting new KMP targets in Compose 1.9