3 ms·
It's possible to wrap UIKit in SwiftUI (using UIViewRepresentable and UIViewControllerRepresentable), to do the things that SwiftUI can't yet do by itself. Thos
by fractallyte 4y ago
It's possible to wrap UIKit in SwiftUI (using UIViewRepresentable and UIViewControllerRepresentable), to do the things that SwiftUI can't yet do by itself. Those deficiencies will slowly be filled out, of course - there's no reason to stay exclusively with UIKit any more.
More significantly, SwiftUI introduces a new declarative paradigm - very different from what was before. It makes a lot of previously laborious things, easy.
So, yes - SwiftUI is the way to go, and it's ready to use now.
- saagarjha 4y agoOn iOS. The situation is very different on macOS, which is what was being discussed here.
- myko 4y agoThese APIs exist for NSView (AppKit) as well: https://developer.apple.com/documentation/swiftui/nsviewrepresentable https://developer.apple.com/documentation/swiftui/nsviewrepr... https://developer.apple.com/documentation/swiftui/nsviewcontrollerrepresentable https://developer.apple.com/documentation/swiftui/nsviewcont... Or is that not what you meant?
- saagarjha 4y agoYeah, I mean that it’s not ready to go.