4 ms·

Loving this so far, I've been working with it for a week now. I have a personal app, DownPay for iOS, that is built with SwiftUI that I want to bring to Android

Loving this so far, I've been working with it for a week now. I have a personal app, DownPay for iOS, that is built with SwiftUI that I want to bring to Android. I tried going the React Native route to build an android-only version but the context switching between SwiftUI, React Native, and then my day job made it challenging. I also tried Ionic and Ignite and wasn't successful with those either. After testing the feasibility of other cross-platform frameworks, I landed on Skip. I LOVE that I don't have to break out of the "Swift" mental context, I just have to focus on writing an app in 1 language. So before I commit fully I've been testing it out (building a demo app this week) and so far I am very impressed. The syntax to write platform-specific code (#if !SKIP #endif) is very easy to use once you get the hang of it. It's amazing I don't have to learn Android to get something up and running at this speed with Skip. Hitting run in xcode and watching both emulators open feels like magic. I want to put this to the test so I plan to build a complete App with it from start to finish, ship it to both App Stores, and if all that goes smoothly I will proceed to migrate my main app using Skip.

AnonHP 2y ago
> It's amazing I don't have to learn Android to get something up and running at this speed with Skip Any thoughts on how you would debug issues on Android that don’t show up on iOS?
- abewhite 2y ago
  Skip generates native code, so you can open it in Android Studio and use all the native debugging tools
  - nprateem 2y ago
    If you know how given the point of this is not having to learn android
    - raydev 2y ago
      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.
    - marcprux 2y ago
      > 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.
  - evereverever 2y ago
    So every version you release you'll have to go back and fix the same bugs? Or re-patch them in some way?
    - abewhite 2y ago
      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/ https://skip.tools/docs/platformcustomization/

AnonHP 2y ago

> It's amazing I don't have to learn Android to get something up and running at this speed with Skip Any thoughts on how you would debug issues on Android that don’t show up on iOS?

abewhite 2y ago
Skip generates native code, so you can open it in Android Studio and use all the native debugging tools
- nprateem 2y ago
  If you know how given the point of this is not having to learn android
  - raydev 2y ago
    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.
  - marcprux 2y ago
    > 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.
- evereverever 2y ago
  So every version you release you'll have to go back and fix the same bugs? Or re-patch them in some way?
  - abewhite 2y ago
    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/ https://skip.tools/docs/platformcustomization/