JetBrains Changes How Kotlin and Swift Work Together

JetBrains is removing Swift IDE features from its Kotlin Multiplatform plugin, changing the workflow for developers building iOS apps with Kotlin.

JetBrains has announced a significant change for developers using its popular Kotlin Multiplatform (KMP) technology to build applications for both Android and iOS. According to a post on the official JetBrains Blog, the company will discontinue Swift language IDE support within the KMP plugin. This change will take effect starting with IntelliJ IDEA version 2026.3 and Android Studio version Rabbit 2. The removal specifically targets features like syntax highlighting, code editing, and cross-language navigation between Swift and Kotlin files. However, JetBrains clarified that essential functionality will remain. Developers will still be able to run iOS applications and, crucially, debug their Kotlin code on iOS simulators and devices directly from their JetBrains IDE. The core capabilities of Kotlin/Native, which enables Kotlin to interoperate with Swift, are not affected by this decision. This is purely a change to the developer tooling and integrated experience, not the underlying technology that makes KMP work on Apple platforms.

The practical impact of this decision is a more fragmented workflow for mobile development teams. Previously, a key benefit of the KMP plugin was the ability to work on both shared Kotlin business logic and iOS-specific Swift code within a single, unified environment like IntelliJ IDEA or Android Studio. This allowed for seamless navigation, refactoring, and a consistent developer experience. With the removal of Swift support, developers will now be forced to use their JetBrains IDE for Kotlin development and switch to Apple's Xcode for any significant work on the Swift side of their project. This introduces a constant context switch between two different applications, each with its own user interface, keyboard shortcuts, and feature set. The cognitive load associated with this switching can reduce developer productivity and introduce friction into the development cycle. Features that previously bridged the two languages, such as finding where a Kotlin function is used in Swift code, will no longer be available within the JetBrains IDE.

This move likely reflects a strategic decision by JetBrains to refocus its engineering resources. Maintaining a high-quality, full-featured IDE for a language that is rapidly evolving and controlled by another major technology company—in this case, Apple's Swift—is an immense and costly undertaking. By stepping back from full Swift support, JetBrains can concentrate its efforts on strengthening the core Kotlin language, its compiler, and the KMP framework itself. It may also be an acknowledgment that for complex UI development and leveraging the latest iOS platform features, developers are often already working primarily within Xcode. In this view, attempting to replicate Xcode's entire feature set within the KMP plugin was a battle of diminishing returns. This decision aligns with a broader industry trend where tool-makers focus on their core competencies rather than trying to build a single, monolithic solution for every aspect of a complex workflow, instead relying on developers to use the best tool for each specific job.

For teams currently invested in Kotlin Multiplatform, this change necessitates an adaptation of their internal processes. The promise of a single IDE for cross-platform work is now diminished, and development workflows will need to be updated to efficiently manage the handoff between IntelliJ/Android Studio and Xcode. This could make onboarding new developers slightly more complex, as they will need to be proficient in both environments. For organizations that are still evaluating KMP against other cross-platform solutions like Flutter or React Native, this becomes a new consideration. While KMP's core value proposition of sharing logic while using native UIs remains intact, the developer experience is taking a notable step back. Going forward, teams should watch for community-led initiatives or third-party tools that may emerge to bridge the new gap in the tooling chain. The most critical takeaway is that while the development process will become less convenient, the ability to build and ship KMP applications for iOS is not fundamentally compromised.

This change directly impacts developers using Kotlin Multiplatform for iOS apps. They will lose the convenience of a unified IDE experience for both Kotlin and Swift code, forcing them to switch to Xcode for Swift editing and creating a more fragmented development workflow.

For companies using Kotlin Multiplatform, this move could slow down development cycles for iOS targets. Teams may face reduced productivity as developers juggle multiple tools, potentially increasing project timelines and costs. It also signals a strategic shift from JetBrains that could influence future technology stack choices.