If I'm using jetbrains compose with my android pro...

# compose

[Colton Idle]

If I'm using jetbrains compose with my android project is there an easy way to see what compose version I'm actually using so that I know which versions of accompanist to use?

[Garret Yoder]

You'd look in the gradle file to see which version is linked

[Colton Idle]

well. for example im using

compose-plugin = "1.5.11"

but jetpack compose doesn't go to 1.5.11. Maybe theres a jetbrains compose to jetpack compose mapping somewhere

[Garret Yoder]

look for the version ref of things like compose ui and compose core.

Depending on what project template you used, you may also have a .toml file that defines all these where you can find the base compose version

[Garret Yoder]

for example, compose-ui = { module = "androidx.compose.ui:ui", version.ref = "compose" }

and then compose = "1.5.4" from one of my own projects.

[Colton Idle]

interesting. didn't know there was a compose-plugin version AND a compose version. still got a lot to learn in this kmp journey. lol thanks garret

[Albert Chang]

Note that you shouldn't specify the version of Jetpack Compose in a module that already uses Compose Multiplatform. You should instead check here for the mapping.

[jw]

I don't think that advice is strictly true. In fact, I would give the exact opposite advice. The compiler releases more frequently than the Gradle plugin. By specifying a separate entry in your toml tools like renovate can update the compiler at a more rapid pace than the whole suite of artifacts are released. This also means you can hop on new Kotlin versions sooner.

[jw]

We always specify both the AndroidX and JetBrains compiler explicitly so as to take advantage of these faster updates.

[Albert Chang]

Ah I mean dependencies except compose compiler, like androidx.compose.ui, which is what OP is asking.

[jw]

Ah yeah got it. I guess since JB has unified versioning for all that so there's no point in specifying anything except the plugin + compiler.