Swift Academy Podcast — Episode 6, Season 2
Meet the New Swift Android SDK
Swift is no longer just for Apple platforms. A conversation with Joannis Orlandos — CTO and member of the Swift.org Android Work Group — on one of the most consequential announcements in the Swift ecosystem.
“Swift was always capable of running beyond Apple platforms. Now, for the first time, the ecosystem is organized to make it real — not as a curiosity, but as a first-class target.”
Watch the Episode
About This Episode
For years, Swift developers have asked the same question: what if we could write Swift code and ship it to Android? With the announcement of the official Swift Android SDK, that question is no longer hypothetical. Swift has a formal cross-platform path — backed by a dedicated work group, a growing contributor base, and measurable engineering progress.
In this episode of the Swift Academy podcast, we sit down with Joannis Orlandos, CTO and active member of the Swift.org Android Work Group. Joannis was at the center of this effort from its early days, and he brings both the technical depth and the strategic clarity needed to understand what the SDK actually is, where it stands today, and where it is going.
If you have ever dreamed of writing mobile development logic in Swift and deploying it across iOS and Android with a shared codebase, this episode will reframe how you see Swift’s future as a platform-agnostic language.
Key Discussion Points
- How the Swift Android Work Group was formed and what governance looks like for an official Swift platform effort
- The architecture of the new Swift Android SDK and how it plugs into the Android build system
- What “25% package compilation” means in practice — and why it is a meaningful milestone
- The JNI bridge, CMake integration, and the tooling challenges that define the current frontier
- How Swift can co-exist with — and potentially compete with — Kotlin in the Android ecosystem
- The long-term vision for Swift cross-platform apps that share business logic across all targets
- What the Swift community needs to do next to make this a mainstream reality
A Deep Dive into the Episodes’s Themes
Why Swift on Android Matters
Swift is one of the most expressive, safe, and performant languages in production today. But until now, its reach has been bounded by Apple’s platforms. The Swift Android SDK changes that calculus. It is not just a technical experiment — it is a statement about Swift’s ambition as a general-purpose systems language capable of targeting any modern platform.
For iOS developers, this opens the door to sharing core logic — networking, data models, business rules, cryptography — across both platforms without rewriting it in Kotlin or Java. For organizations running heterogeneous mobile teams, it reduces the cost of maintaining two parallel codebases that solve the same problems twice.
- The business case for Swift cross-platform in mixed iOS/Android teams
- How shared Swift modules can reduce duplication across mobile platforms
- Why this matters beyond individuals developers — the ecosystem-level implications
Technical Challenges: JNI, CMake, and Interoperability
Bringing Swift to Android is not a matter of flipping a compiler switch. The Android platform has its own build system, its own native interop layer (JNI), and its own expectations for how native code is packaged and loaded. Joannis walks through each layer of the challenge with precision and without sugarcoating what is still unsolved.
- JNI (Java Native Interface): How Swift code exposes symbols that Android’s Java/Kotlin runtime can call, and the ergonomic friction this introduces today
- CMake integration: Fitting Swift into Android’s native build pipeline, and what the toolchain looks like end-to-end
- Interoperability: Bridging Swift types and memory management with the JVM garbage collector — the hardest problem in the stack
- Build tooling: The current state of Swift Package Manager support for Android targets and what remains to be standardized
Swift vs Kotlin: Competition or Coexistence?
Kotlin is the dominant language on Android, and for good reason — it is expressive, well-supported, and deeply integrated into Google’s toolchain. So where does Swift vs Kotlin actually stand, and is competition even the right frame?
Joannis argues that the more productive framing is interoperability. Swift is not trying to replace Kotlin on Android — it is trying to participate in the same projects. A Kotlin UI layer calling a Swift business logic module is a realistic near-term outcome, not a distant fantasy. The SDK is designed with this composability in mind.
- The realistic near-term model: Swift for shared logic, Kotlin for platform UI
- How Swift’s type system and concurrency model compare to Kotlin Coroutines in cross-platform scenarios
- Why the “one language for everything” framing misses the point of what the SDK enables
Progress & Current State: 25% Package Compilation
The headline figure from the work group’s recent progress update is striking: 25% of Swift packages already compile successfully for Android. For a platform target that is less than a year into serious investment, that number signals genuine momentum — not a demo, not a proof of concept, but real packages running on real Android hardware.
Joannis contextualizes what this means: which categories of packages compile cleanly today, what the remaining 75% is blocked on, and how the work group is prioritizing the remaining surface area.
- What kinds of Swift packages compile today: pure Swift logic, protocol-heavy code, value types
- What is still blocked: packages with platform-specific Apple imports, C++ interop dependencies, and Foundation assumptions
- The roadmap for closing the gap and the milestones the work group has set for the next six months
The Future of Cross-Platform Swift
The Swift Android SDK is the first chapter of a longer story. Joannis shares his vision for where Swift cross-platform development goes from here — including what a mature, production-ready Android target would look like, how the Swift Package Manager ecosystem needs to evolve, and what role the community plays in accelerating the timeline.
- A realistic timeline for production-grade Android support in Swift
- The role of community package maintainers in expanding Android compatibility
- How the Swift Android Work Group interfaces with Apple, Google, and the open source community
- What a world with first-class Swift cross-platform tooling looks like for mobile development in 2026 and beyond
Resources & Links
About the Guest
Joannis Orlandos
CTO • Member, Swift.org Android Work Group
Joannis Orlandos is a systems-level Swift engineer with deep expertise in low-level networking, server-side Swift, and cross-platform tooling. As a member of the official Swift Android Work Group, he is one of the engineers actively shaping how Swift expands beyond Apple’s platforms. His work spans open source Swift packages, compiler toolchain contributions, and the foundational infrastructure that makes the Swift Android SDK possible. He brings both the rigor of a CTO and the hands-on engagement of a core open source contributor to everything he does.
Key Takeaway
The Swift Android SDK is not a distant promise — it is an active engineering effort with a governance structure, measurable milestones, and real momentum. Twenty-five percent of Swift packages already compile for Android. The tooling is taking shape. The work group is organized and moving fast.
For Swift developers, this is the moment to pay attention. The skills, patterns, and packages you build for Apple platforms today are closer to being Android-portable than they have ever been. Joannis’s work, and the work of the broader Swift Android Work Group, is turning Swift cross-platform mobile development from an aspiration into an engineering roadmap.
Listen & Subscribe
If you care about the future of Swift beyond Apple platforms, this is one of the most important conversations happening in the ecosystem right now. Share it with your team, your fellow iOS developers, or anyone who has ever asked: “Why can’t we just use Swift on Android?”
Subscribe to the Swift Academy podcast for weekly conversations at the intersection of iOS development, software architecture, and the evolving Swift ecosystem.