I’d actually recommend your setup, because the whole team can edit and contribute to Kotlin.Ĭould publishing KMM code through SPM be quicker than our assemble step?That depends. Often, the KMM is sort of just a “trial” and requiring a bunch of new tooling and build time is a lot for something that the team hasn’t really committed to. The CI pipeline for iOS is already complex and/or doesn’t easily incorporate Kotlin/Gradle.The iOS team has no experience with JVM/Gradle and the dev setup is creating issues.Most of the iOS team wouldn’t be editing Kotlin so the extra build is frustrating.
When we started working with teams who haven’t been doing KMM, there is often pushback to introducing KMM into the build pipeline for a variety of reasons. What I’ve read here and there is that Touchlab recommends the latter option, by publishing KMM code as a Swift Package to a GitHub repository and then pulling it in into the XCode project.We recommend that only for teams that aren’t using KMM at all and refuse to introduce the local build step.
0 kommentar(er)
