appkit-swiftui-bridge

To integrate SwiftUI views into an AppKit application, you host them using NSHostingView and NSHostingController, which facilitates gradual migration without a full rewrite. This enables seamless interoperability between both frameworks.

The best way to wrap an AppKit NSTableView for use in SwiftUI is by using NSViewRepresentable. This protocol lets you bridge existing AppKit views into SwiftUI hierarchies while maintaining their original functionality.

State management when bridging AppKit and SwiftUI relies on synchronizing data using @Observable, Combine, or NotificationCenter. These patterns ensure state stays consistent across both frameworks during incremental adoption.

Yes, you can incrementally adopt SwiftUI in a mature AppKit codebase by embedding new SwiftUI components using hosting controllers. This approach allows you to introduce new features without requiring a complete rewrite.

You need NSViewRepresentable when you want to leverage existing AppKit capabilities from within a SwiftUI hierarchy. It is required for wrapping AppKit views like NSTextField or NSTextView so they function properly inside SwiftUI.

Bridged AppKit views may not update because state management is not properly synchronized. You must connect the AppKit view to SwiftUI using @Observable, Combine, or NotificationCenter to ensure data updates propagate correctly.