The Swift open-source project community has released the first preview of the official Android SDKThis step allows developers to program native Google apps using the language created by Apple. The move opens the door to new cross-platform workflows, something especially interesting for development teams in Spain and the rest of Europe.
After years of using separate tools and languages, teams will be able to share the same business logic in Swift across iOS and AndroidMaintaining native user interfaces on each platform. This is a Nightly Preview version, but with enough documentation, examples, and community support to get started without workarounds.
What does the new SDK include and how is it designed?
The launch comes in partnership with Android Workgroup within the Swift project, which has coordinated months of work to offer stable tools, documentation, and support. According to the announcement, the SDK is available as part of the Swift installer for Windows and also in standalone packages for Linux and macOS.
In addition to the SDK itself, a Step-by-step starter guide which covers package installation and project structure. Developers have access to sample repositories on GitHub that demonstrate the integration of Swift code inside Android apps already existing, which reduces adoption friction.
The focus is on reusing the functional part of the application: business rules, calculations, and data handling They are written only once in Swift. The visual layer, however, remains native; on Android, tools like Jetpack Compose will continue to be used, and on iOS, Apple's usual tools will be used. In other words, it is not included SwiftUI for Androidavoiding hybrid interfaces that break with local design guidelines.
Interoperability between languages ​​is achieved thanks to swift-java, a project that It automatically generates secure, high-performance links. between Swift and Java to call Android APIs without complex configurations. This bridge allows you to combine the performance of native Swift code with the extensive Android library ecosystem.
The Swift Package Index already labels modules with Android compatibility and more. 25% of the packages They are currently compiled for this platform. This facilitates the reuse of components and accelerates the implementation of real cross-platform projects.
Impact on teams in Spain and Europe
For local businesses and teams, especially SMEs and startups, the SDK opens up the possibility of unify the core of the apps and reduce time to production. Maintaining a single logical base helps align functionalities, minimize divergent errors, and optimize budgets in tighter development cycles.
In the European ecosystem, where demanding regulations and a wide variety of Android devices coexist, being able to Sharing validations, flows, and data models in Swift It provides consistency without sacrificing native interfaces. This also facilitates simultaneous release schedules between iOS and Android.
The community has reacted with interest in specialized forums, highlighting that the commitment to shared code without imposing the UI It avoids one of the most common problems with multiplatform solutions: interfaces that "don't feel" native.
The Android Workgroup invites European developers to join the debate, share tools and experiences and contribute to the project roadmap. Open participation is key to prioritizing improvements with an impact on real-world contexts in the region.
Project status, current limitations, and next steps
It is worth remembering that we are dealing with a Preliminary version updated nightlyAlthough the SDK already allows you to compile and run apps, there are still areas to polish and features to come, with a work plan visible on the project's channels.
The working group is preparing a vision document This will guide priorities and provide an initiative dashboard to measure progress. Continuous SDK integration is also being strengthened to ensure stability and traceability in each iteration.
Since SwiftUI is not included, the strategy involves maximize interoperability and the quality of the bridge with Android, ensuring seamless data and call exchange. This approach preserves native performance and the expected user experience on each system.
Prominent figures in the community, such as Joannis Orlandos, have emphasized that the milestone is the result of months of coordinated work and years of previous contributions, and invite the community to continue feeding the project with feedback and use cases.
How to get started if you develop for iOS and want to move to Android
If you already work with Swift on iOS, the recommended path is to install the SDK via Windows installer or download the packages for Linux and macOS, and then follow the official Getting Started Guide to set up the environment and project structure.
The example repositories show Complete Android flows written in SwiftThis includes integration with Swift Java to link to existing system APIs and libraries. Reviewing these examples accelerates the learning curve and helps avoid common mistakes.
From there, the goal is to extract the business logic of your iOS app to shared modules in Swift and connect that layer with the native Android interface. This separation will allow you to maintain consistent visual identities across all stores and platforms.
For questions and issues, the Swift forums and Android Workgroup spaces are the place to go. share problems, tools, and improvementsContributing compatible packages or specific guides for European cases (e.g., localization or formats) can have a significant impact.
With a solid technical foundation in place, the Swift SDK for Android is shaping up to be a solid path to accelerate launches and align functionalities across platforms, maintaining the best of each ecosystem: native performance, consistent interfaces, and a modern development stack.
