

We wanted to avoid all the headaches that Android developers typically have to suffer when working with these tools. We realized that we could optimize the many of the hassles present in developing in Swift for Android and at the same time, improve the experience for our developers in this area. One of the biggest hurdles in using Swift compiler for Android is the lack of official support from Apple, which means no continuous integrations or no official builds.


But SwiftFoundation on the other hand is not the same Foundation that Apple uses for its own platforms it’s a re-implementation of all classes from the original library. SwiftCore and Dispatch are largely identical to iOS and Mac versions. We only have access to SwiftCore, Dispatch, and SwiftFoundation in our toolchain. Moreover, it’s actually better for developers, because they can re-use most of the instruments that were created for C/C++ development - Android profiling tools or an Android low-level debugger (with a limitation on an evaluation of swift code). That’s why, from an Android device perspective, there is no difference in libraries compiled from C/C++ or Swift code. Google already makes use of LLVM compilers for native Android development with C/C++.
