undefined | Better HN

0 pointsdagmx11mo ago0 comments

As with other languages, you’d need bindings to another UI framework. In that sense, I wish SwiftUI had a different name because it seems intrinsic to Swift when it’s really no different than UIKit.

There’s stuff like SwiftCrossUI that does multiple backend bindings

https://github.com/stackotter/swift-cross-ui

And Qt was exploring some bindings using the new C++ interoperability.

0 comments

loic-sharma11mo ago

There’s also Shaft, which is Flutter ported to Swift:

https://github.com/ShaftUI/Shaft

Like Flutter, this paints everything itself. It doesn’t need to bind to a UI framework directly. Instead, it needs the platform to provide primitives like a surface to draw into and input events.

j / k navigate · click thread line to collapse