"You got Kotlin in my iOS." "You got Swift in my Android."
Perfectly delivered, the Reese's commercial that keeps on giving. Although to fully match the analogy, there'd need to be some form of Kotlin+swift hybrid with a crinkly wrapper.
The Swift SDK for Android
51–60 of 298 posts
Re: The Swift SDK for Android
#52> Over 25% of packages in the Swift Package Index already build for Android That's... not encouraging.
If you compare it to absolute zero I think you may be pleasantly surprised.
Re: The Swift SDK for Android
#53This is really interesting. I’ve made cross platform mobile libraries before and ended up using Rust… which was fine. But there’s a huge built in advantage to using a language one half of the problem is already fluent in. Curious to see how well it combines with Swift/Webassembly.
Re: The Swift SDK for Android
#54I'm a big lover of Kotlin Multiplatform, but I think this is pretty cool anyway. I could imagine making a native Swift library shared between the platforms for memory-sensitive work. I'm not sure about using it to write an app's entire business logic, KMP is going to be more mature for a while for this.
Do you build desktop apps, too, with Kotlin Multiplatform? How mature is it overall?
Re: The Swift SDK for Android
#55I think people will get excited about this and then quickly realize how painful it is to code in a foreign environment from the platform. How miserable it would be trying to write Java or kotlin targeting iOS apps. I think this will be the same. Just use the native tools and languages for the platform. Swift/Objc/xcode for iOS. Java/Kotlin/Android Studio for Android. You will be so much happier.
> How miserable it would be trying to write Java or kotlin targeting iOS apps. I think this will be the same.
What happens in the Java/Kotlin case?
Re: The Swift SDK for Android
#56Very 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 t…
This is already possible with .NET and MvvmCross: a shared core library plus native UI projects for each platform. UIKit feels great in C# and it’s all been working quite well since Xamarin times, with access to the Nuget ecosystem.
Re: The Swift SDK for Android
#57Does this result in the Swift code being compiled or transpiled?
Re: The Swift SDK for Android
#58Thank you. Please kill RN and Flutter already. I'm done with square UI apps that handle touches after two days
You can set the corner radius to whatever you like in Flutter, also the framework is quite fast, if an app doesn't respond to touches it's likely a poorly made app
Re: The Swift SDK for Android
#59"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? https://kotlinlang.org/docs/native-overview.html
How solid is Kotlin on iOS?
Re: The Swift SDK for Android
#60Interesting to see excitement around this release...
BUT beyond cross‑platform hype there's a practical question... what developer tooling will look like... Are we getting first‑class debugging, package management, continuous integration for Android targets...
ALSO adoption often comes down to licensing and governance... open SDKs thrive when the steering group is transparent and responsive...
And it's worth remembering that bridging two ecosystems isn't just about code... it's about aligning design idioms, APIs and expectations... Without that you end up with uncanny valley apps...