Will Swift Conquer Android? Inside Apple’s New Android Workgroup

Opening: Quietly Doing Big Things

Without a launch event or marketing hype, Apple quietly announced on June 25, 2025 that the Swift Open‑Source project has created a Swift Android Workgroup, whose direct goal is to make Swift run natively on Android.

Why Adapt Swift to Android?

Swift was originally created to unify Apple’s ecosystem—from iOS and macOS to Linux and Windows, and even Vision Pro and server‑side apps. Ignoring the Android market, which powers roughly 3 billion active devices, would be impossible for any serious app. Dual‑platform development remains the norm, causing developers pain.

If Swift can truly unify both platforms, developers gain a powerful tool and Apple could extend its influence beyond iOS, potentially reducing Android’s user experience quality. The competition is not just on the front lines; winning developers is a deeper strategic move.

What the Swift Android Workgroup Is Doing

The workgroup, now an official part of the Swift community, has a clear roadmap:

Integrate Android into the official Swift build system.

Develop and maintain an Android‑compatible Swift toolchain.

Define supported Android versions and ABIs.

Improve debugging, JNI interaction, and CI testing.

Enable core Swift libraries such as Foundation to run on Android painlessly.

In short, Apple wants Swift to be a first‑class language on Android, and the effort is already underway.

Kotlin’s Position

Kotlin, Google’s “first‑child” for Android, has been a first‑class citizen since 2017, deeply integrated into Android Studio, Jetpack, Compose, and Kotlin Multiplatform (KMP).

Although Kotlin’s future on Android is not yet at risk, its ownership lies with JetBrains rather than Google, whereas Swift benefits from Apple’s direct control and ecosystem integration. If Google does not push Kotlin onto server‑side and other platforms, Swift’s expanding ecosystem could pressure Kotlin.

Comparison of the two language ecosystems:

Kotlin Multiplatform (KMP) strengths:

Backed by JetBrains and Google, emphasizing shared business logic.

Coroutines offer flexibility but are low‑level.

Jetpack Compose provides cross‑platform UI, though still maturing.

Swift strengths:

Structured concurrency (async/await, actors) with enforced thread safety and state management.

Proven on iOS, server‑side, and SwiftUI.

Apple’s direct stewardship gives a tightly integrated ecosystem.

This language rivalry is just beginning.

Community Reaction

Android developers: “Finally we can write in the most elegant language!”

Kotlin loyalists: “Swift may be great, but it’s still Apple’s. Is Apple trying to take on Flutter, Kotlin, React Native all at once?”

Support for Swift on Android could shift some Android developers toward Swift, especially those seeking cross‑platform code reuse. Teams that master both Swift and Kotlin may reduce development costs, while Kotlin may feel pressure to evolve.

Impact on Individual Careers

Whether you are an iOS or Android developer, or a team lead, the rise of Swift on Android will likely increase demand for Swift expertise. Learning Swift alongside Kotlin could double a developer’s skill set and boost market value.

A possible workflow: write core logic (network, business, models) in Swift, implement UI natively—Kotlin for Android, SwiftUI for iOS—thus preserving native experience while sharing code.

Conclusion: Will Kotlin Fade?

Swift’s move to Android is not merely a “cross‑platform language” experiment; it is a strategic expansion of Apple’s ecosystem that will reshape developer skill stacks and cross‑platform development patterns, presenting both challenges and opportunities for Kotlin.

Google will likely continue to invest heavily in Kotlin, improving Jetpack Compose and other tools, but Swift’s Android support introduces a serious competitive dynamic that could ultimately benefit developers and users through richer choices.