The Android Workgroup is hosting another bi-weekly meeting 2026-04-22T16:00:00Z→2026-04-22T17:00:00Z. The workgroup meetings are free for anyone interested to join. Feel free to chime in, or just listen to the topics and discussions.
Post any topics you'd like to discuss here or on the Swift Open Source Slack.
I had a lot of interest in the Swift SDK for Android at https://tryswift.jp last week! It's a great and cross-platform minded community, so hopefully we'll materialize more community there.
1 Like
If there is a bit of time available, I’d love to share details on some exciting news.
Cricut has been using various Swift Android toolchains for a few years now in our Design Space product. Particularly, we use them as part of a code generation system that mirrors Swift interfaces in Kotlin, TypeScript, C#, and Dart. The system allows sharing Swift code with those languages in a way that is compatible with several development toolchains and operating systems, including Windows, macOS, Linux, Android, and iOS, as well as Electron by way of WASM.
The exciting news is: we’re in the process of releasing the system as an open source project! That would allow anyone to export an existing Swift library code as a Kotlin library, compatible with Android development!
We use the system with Android Studio to publish our Design Space app, used by millions of users, and have matured the technology in that demanding environment. We hope that by making the tool open source, we can work with the community to mature the system further, while giving community members access to a powerful tool for cross-platform software development. We (at Cricut) intend to continue using the system to power the libraries in our software products, and hope the community can benefit from it with us!
The call looks to have 4 topics already, so there may be no time to discuss this, but this seemed like the group that would have interest in an open-source bindings generation tool.
5 Likes
Some more topics:
-
Following on the move to build the trunk SDK against API level 24, plan any further Android API level changes.
-
The SwiftPM team are planning swift sdk changes that affect all SDKs, including of course Android, with one of those pulls just merged. Sound off on any further changes wanted, as Android users are likely the main users of this SwiftPM subcommand.
-
Trunk SwiftPM just switched to swift-build as the default build system backend, which raises some issues for SDKs and Android, so we'll have to hash out how to approach that.
-
I'm told that some SwiftPM devs finally got the swift sdk subcommand working on Windows, so we can reuse the trunk SDK bundles with the trunk Swift toolchain for Windows too. We should discuss how to handle that there may now be two ways to install differently-structured Android SDKs with the trunk Swift toolchain for Windows.
-
We've been hitting some issues with the clang resource directory, a required directory from the clang toolchain for a platform, that we've been addressing in various ways. Explore if we can come up with a better way forward.
The call looks to have 4 topics already, so there may be no time to discuss this
I'm sure we can fit it in, we'll just need to prioritize and move topics around, plus make sure we don't go too long on any one topic.
1 Like
