Skip.tools
-
|
One of the most appealing features of Skip for me is ejectability. If I decide that I want to stop using Skip and switch to developing a native Android app, I can run the Skip transpiler for the last time and "eject" from the Skip ecosystem, maintaining my Android app in native Kotlin. Ejecting provides an insurance policy, guaranteeing that I won't get "stuck" with Skip in the future. https://skip.tools/docs/native/ lists a number of advantages and disadvantages of native compiled Swift. But, am I right in thinking that a Swift app that was compiled to Android would have no way to eject on the Android side? I'm not going to be able to maintain a compiled binary in Android Studio. I'd either have to go back to transpiling or give up on ejecting. If I have that right, then I think it should be called out as a disadvantage of compiled Swift in the documentation. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
You raise a valid point. While creating a native Swift library for Android is something that can be done with the open-source Swift Android SDK, in order to be able to go back and forth between the Kotlin and Swift easily is dependent on the bridge-creation capabilities of the skipstone plugin, which you would no longer be using if you eventually decide to eject you code. I'll update the native docs to mention this. Thanks for pointing it out. |
Beta Was this translation helpful? Give feedback.
You raise a valid point. While creating a native Swift library for Android is something that can be done with the open-source Swift Android SDK, in order to be able to go back and forth between the Kotlin and Swift easily is dependent on the bridge-creation capabilities of the skipstone plugin, which you would no longer be using if you eventually decide to eject you code.
I'll update the native docs to mention this. Thanks for pointing it out.