Question 1

How do I wrap an AppKit view for use in SwiftUI?

Accepted Answer

Implement NSViewRepresentable with makeNSView to create the AppKit view, updateNSView to sync SwiftUI state, and makeCoordinator for delegate callbacks. Use sizeThatFits on macOS 13+ to control layout and dismantleNSView to clean up observers.

Question 2

How do I embed a SwiftUI view in an existing AppKit app?

Accepted Answer

Use NSHostingView to place SwiftUI inside an existing NSView hierarchy, or NSHostingController when you need a full view controller for sheets, split views, or windows. Set sizingOptions explicitly and update rootView when data changes.

Question 3

When should I use NSViewRepresentable instead of pure SwiftUI?

Accepted Answer

Use NSViewRepresentable when SwiftUI lacks a native equivalent, such as NSTextView rich text editing, or when performance requires AppKit, like NSTableView with over 100k rows. Go pure SwiftUI when full API coverage exists on macOS 14+.

Question 4

How do I share state between AppKit and SwiftUI?

Accepted Answer

On macOS 14+, share an @Observable class and use withObservationTracking on the AppKit side. For older targets, use a Combine ObservableObject with @Published properties and sink subscriptions, always dispatching UI updates to the main thread.

Question 5

Why does my NSViewRepresentable coordinator cause a retain cycle?

Accepted Answer

Retain cycles happen when Combine sinks or callbacks capture self strongly, or when the coordinator's parent reference is never refreshed. Use [weak self] in closures, update coordinator.parent in updateNSView, and invalidate observers in dismantleNSView.

appkit-swiftui-bridge

SYSTEM DOCUMENTATION & REQUIREMENTS

Frequently Asked Questions about appkit-swiftui-bridge

Related Skills

appkit-swiftui-bridge

macos-appkit-interop

debugging-instruments

swiftui-patterns