Related: https://skip.tools <-- SwiftUI for Android
The Swift SDK for Android
41–50 of 298 posts
Re: The Swift SDK for Android
#42Does this project tie in to the SKIP transpiler? https://skip.tools/blog/bringing-swift-to-android/ I have an existing Swift / SwiftUI app that I am looking to port to Android, and have been not wanting to move to React Native.
You don't need to use the transpiler anymore. Skip added native Swift execution on Android recently. It has much greater compatibility than the transpiler (though they maintain both).
Re: The Swift SDK for Android
#43Earlier quoted context omitted.
Thanks - I see, so swift packages for everything. What would be the equivalent shader / GPU language on Android? OpenGL?
OpenGL or Vulkan, you might be able to have some luck transpiling metal shaders to spirv-cross at a cursory look
Sometimes it is easiest to have an agent like Codex rewrite the shader instead...
Re: The Swift SDK for Android
#44Why can’t everything just be a progressive web app
Because Google/Apple don't want us to circumvent their respective app stores, so they make certain features/API's a PITA (if not impossible) to use unless you are building natively.
Re: The Swift SDK for Android
#45I would love if I don't have to port my whole iOS app to Android manually. How exactly would this integration work if say business logic is handled by Swift - I'm guessing UI and SwiftUI would not be supported initially? My app [0] uses a lot of metal shader code - I'm guessing there's no easy way to bring that across? [0] https://apps.apple.com/app/apple-store/id1545223887
Yeah I would also like to see SwiftUI but its apple ecosystem only.
https://skip.tools ported SwiftUI to Android.
Re: The Swift SDK for Android
#46"You got Kotlin in my iOS." "You got Swift in my Android."
Kotlin on iOS is statically compiled and interops with Swift/ObjC natively. Don't think KMP on iOS is even running a VM like Flutter has to with Dart?
Re: The Swift SDK for Android
#47Very excited to see this as an official project!
I've been toying around with multiplatform frameworks like RN and Flutter for a side project of mine but they never feel right. I'd rather use the native UI per platform and have a nice way to share business logic. KMP exists but I think for most developers wanting to build an app it's more common to build for iOS first, and then port to Android later if the app gets traction. With a little foresight of keeping shared code in a Swift Package, it seems like that's getting more and more possible which is great to see.
Re: The Swift SDK for Android
#48I hope they actually stick with this. Swift embedded, for example, is a sort of proof of concept more than viable platform, and you end up battling that more than the problem you are trying to solve. It is a shame because aesthetically Swift is easily the nicest of the modern safe languages, but there have been really odd noises in the community about project leadership that sour things.
[deleted]
Re: The Swift SDK for Android
#49Re: The Swift SDK for Android
#50This looks like a Fluttter competitor where the UI is rendered by the Swift SDK side (vs Android-provided library).