top | item 41385469

(no title)

nyrulez | 1 year ago

tbh this is the main thing I was looking for on the webpage. It's hard for me to jump ship from my existing workflows unless I see a professional and highly sophisticated app example. I am sure it works for simple cases but I am concerned about limitations that one hits as one does more complex things

discuss

order

marcprux|1 year ago

Out of curiosity, what are your existing workflows?

Note that Skip doesn't put any constraints on the iOS side of your app at all: if it can be expressed with SwiftUI or UIKit, then you can do anything. If there are bits that SkipUI doesn't translate to your liking (or at all), you can always drop down directly into Kotlin and Jetpack Compose to implement those any way you want. See https://skip.tools/docs/platformcustomization/ for details.

yumraj|1 year ago

How does it work in practice?

In other words the Swift app will keep developing, requiring constant Android app generation via transpilation.

Does it keep track of generated and manually edited parts or will that step on each other?