Comment by internetter
1 year ago
That’s ok because it’s simple enough to escape SwiftUI. Use SwiftUI for the simple bits and UIKit for the harder parts. It’s not a nice solution, but it works
1 year ago
That’s ok because it’s simple enough to escape SwiftUI. Use SwiftUI for the simple bits and UIKit for the harder parts. It’s not a nice solution, but it works
I consider use of UIViewRepresentable to be a kludge, and basically removing the advantages of SwiftUI.
I know that SwiftUI has some native wrappers, like maps, but the way that SwiftUI works, is so radically different from UIKit, that I think mixing them is problematic.