Hi ,
Welcome to another week of MobilePro; this is edition no. 197.
Swift on Android is actually happening. Did I think I would be saying that soon? No. But Apple’s Swift team just started rolling out nightly Swift SDKs for Android. For years, Swift was this tightly bound iOS language. Android and Swift lived in different worlds; iOS had a “you do Kotlin, I’ll do Swift” kind of relationship with Android. But now, Swift’s knocking on Android’s door like it’s been saying, in the words of Swift’s popstar namesake, “you belong with me.” The SDK lets you build, test, and even run Swift apps on Android, with interoperability for Java and Kotlin baked in. It’s still early, but this changes how we think about building for both platforms.
Imagine writing your shared logic, that is, networking, models, even business rules, in Swift and reusing that code across iOS and Android builds. You’d still have native UI layers, but the engine underneath could stay consistent. That’s where this SDK nudges us: toward more Swift-first cross-platform development, and not through a framework like Flutter or React Native but via native builds powered by a common language. And since the SDK is being updated nightly, tooling, package compatibility, and documentation should mature fast.
That said, it’s not all smooth roads just yet. Debugging’s still rough, Android Studio isn’t exactly Swift-friendly, and the Java bridge needs some love. But if you’re already deep in Swift, maybe using it on the backend too, then this might be the next logical step. One toolchain, one mindset, less context-switching. Who knows, maybe in a year or two, “Swift everywhere” won’t sound that crazy anymore, fulfilling the Wildest Dreams of mobile devs everywhere.
That’s not all the news this week. Let’s dive in.