3 ms·
It exists already. SwiftUI to Jetpack Compose: https://skip.tools https://skip.tools And a less mature but very interesting project with a SwiftUI-like API fo
by wahnfrieden 1y ago
It exists already.
SwiftUI to Jetpack Compose: https://skip.tools https://skip.tools
And a less mature but very interesting project with a SwiftUI-like API for UI across macOS/Linux/Windows plus some emerging support for Android and even a TUI target contributed by Miguel de Icaza: https://swiftcrossui.dev https://swiftcrossui.dev
> It's a description language that system frameworks interpret and create NSViews and UIViews and CGLayers etc out of.
This is out of date. FYI parts of SwiftUI are "native" now. Notably the new Liquid Glass UI was written in "native" SwiftUI. UIKit and AppKit actually wrap SwiftUI views to render Liquid Glass now. Although SwiftUI-exclusive APIs have always existed, this was a notable step in a new direction and suggests the future of UIKit and AppKit is a unified "native" SwiftUI implementation.
They've also been ripping out UIKit/AppKit implementations of SwiftUI views... IIRC List is no longer a UITableView for instance (could be confusing with another component though).
- dvtkrlbs 1y agoI think using a closed source solution (except the platform native solution) for such a core part of an application is a big no.
- wahnfrieden 1y agoI agree it makes me very nervous. Though as I understand it, it's mostly open source (edit: not the build tool tho). Their transpiler solution at least results in maintainable Kotlin code that one could begin working in directly without needing Skip. But the transpiler way is more limiting than the native Swift SDK on Android. I'm considering using it just as a way to bootstrap as my main focus has been iOS/Mac. If I can use it to generate enough of a new revenue stream on Android, I could then afford to hire an Android developer to take care of doing it without Skip, too.
- dvtkrlbs 1y agoThat makes perfect sense imho. I don't see it as a long term solution.