:wave: We are working on getting compose Multiplatform into our project. Is it crucial to maintain v...

# compose

[Dmitriy Tarasevich]

👋 We are working on getting compose Multiplatform into our project. Is it crucial to maintain version parity between jetpack compose dependencies and Multiplatform versions? For the latest Multiplatform compose versions reference jetpack compose 1.7.0.. does that mean that we cannot use 1.7.3 in modules that are based on jetpack compose?

[Pablichjenkov]

In some cases they are compatible between them so it is ok to compile versus one and include the other in the final build. Usually in this cases only the patch in the semantic version change. This example you post seems to fall in this case 1.7.x "should" be compatible between themselves.
When minor version changes they are most likely not compatible. Eg: 1.6.x and 1.7.x

[Dmitriy Tarasevich]

incompatibilities would most likely result in a runtime error?

[Pablichjenkov]

However, AFAIK the only way to know is building and testing to check everything is working as expected

[Pablichjenkov]

Right, non compatible will lead to errors like function signature mismatch or symbols/classes not found

[Stylianos Gakis]

You're probably gonna add headaches if you try to do this split. Going MP will meant that you will be using the multiplatform dependencies even for android, so yeah, you will sometimes have to wait for that one to catch up with the latest releases which have only been made for Android.

[Dmitriy Tarasevich]

figured as much, thanks for the confirmation guys. It seems like they do a good job updating relatively quick anyways