i have one doubt, as an android dev we have to add...

# compose-ios

[vips]

i have one doubt, as an android dev we have to add compose dependencies like androidx.compose.material3:material3:$version, but in compose multiplatform this libs belongs to jetbrains

val material get() = composeDependency("org.jetbrains.compose.material:material")
val material3 get() = composeDependency("org.jetbrains.compose.material3:material3")

[xxfast]

Well, newer androidx compose dependencies are managed by BOM (bill of materials) and compose multiplatform dependencies are managed by the grade plugin, which is like BOM before BOM was a thing

[vips]

My doubt was, the team is recreating same compose libraries for cross platform from scratch ? Or reusing androidx jetpack compose libraries for other platforms?

[Dima Avdeev]

We are reusing androidx modules.
But we also compile native and js targets.

[vips]

So I can say, Jetpack compose Android team from Google will always be ahead of your jetbrains compose multiplatform team?

[Sergey Y.]

Sure, that’s expected, Google is the original creator of Jetpack Compose, and JetBrains is adding a multiplatform functionality to it, so Jetpack Compose will always have an edge, and there is nothing bad about that.

[Dima Avdeev]

@vips
We communicate with a Google team. They are helping us a lot! I think in the future we will a way more faster implement the same functionality.