Announcing the Android Workgroup
forums.swift.org
Announcing the Android Workgroup
1–10 of 17 posts
Re: Announcing the Android Workgroup
#2(naive question)
Re: Announcing the Android Workgroup
#3Re: Announcing the Android Workgroup
#4Did they finish porting the core lib to Windows?
Re: Announcing the Android Workgroup
#5Re: Announcing the Android Workgroup
#6I always found non-native apps too out-of-place. Please use Swift on iOS and Kotlin on Android.
Re: Announcing the Android Workgroup
#7I always found non-native apps too out-of-place. Please use Swift on iOS and Kotlin on Android.
Swift is just a programming language, I thought?
Unless I am also mistaken, they are seeking to make a supported language to android development.
Which will save mobile devs having to learn two languages, and also allow reuse of code.
Re: Announcing the Android Workgroup
#8Earlier quoted context omitted.
Swift is just a programming language, I thought?
Yes. Unless I am also mistaken, they are seeking to make a supported language to android development. Which will save mobile devs having to learn two languages, and also allow reuse of code.
Re: Announcing the Android Workgroup
#9Earlier quoted context omitted.
Swift is just a programming language, I thought?
Yes. Unless I am also mistaken, they are seeking to make a supported language to android development. Which will save mobile devs having to learn two languages, and also allow reuse of code.
Re: Announcing the Android Workgroup
#10When using Skip Fuse, your Swift code compiles to 100% native Android ARM code.
They've also reimplemented ~60% of SwiftUI on Android, in an open-source library, SkipUI. https://github.com/skiptools/skip-ui SkipUI works way better than you'd think, and anyway, it's totally optional.
You can just write Swift against native Android APIs and it works fine.