Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Skip generates native code, so you can open it in Android Studio and use all the native debugging tools


So every version you release you'll have to go back and fix the same bugs?

Or re-patch them in some way?


You don’t manually edit the generated Kotlin. You change the Swift. And if there are things you can't or don't want to do in Swift, there are mechanisms for writing Kotlin inline in your Swift, dropping Kotlin files into the project, and other platform customization options: https://skip.tools/docs/platformcustomization/


If you know how given the point of this is not having to learn android


> given the point of this is not having to learn android

We wouldn't say that is the point of using Skip. The benefit you get from using Skip is that you can use a single language and a single framework for building your app, and you can iterate on your app's development without needing to constantly context-swift between different worlds.

But there is no denying that at some point, you will need to interact with the Android universe: you will need to run the app on an Android emulator or device to test it, you will need to use Android Studio (or IntelliJ) to run the app in a debugger, you will need to grapple with the Android-specific nuances of deploying you app to the Play Store.


None of the alternatives like RN or Flutter will allow you to skip learning about a specific platform if you have a platform-specific bug or issue.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: