swiftui-uikit-interop

To wrap a UIKit view in SwiftUI, use UIViewRepresentable and implement makeUIView to instantiate the view and updateUIView to apply state changes. This ensures correct lifecycle handling and state synchronization across the boundary.

Capture UIKit delegate callbacks by implementing a Coordinator class inside UIViewControllerRepresentable. The Coordinator acts as the delegate, receives the callbacks, and routes the results back into SwiftUI through @Binding properties.

Embed SwiftUI views inside a UIKit app using UIHostingController. For iOS 16+ table or collection view cells, use UIHostingConfiguration to achieve correct containment, sizing, and seamless integration.

State sync is lost when lifecycle logic is misplaced. Ensure UIKit views are created in makeUIView and updated in updateUIView. Use the Coordinator pattern with @Binding to properly synchronize state and prevent update failures.

Yes, you can incrementally migrate a UIKit app to SwiftUI by wrapping existing UIKit views and controllers with UIViewRepresentable and UIViewControllerRepresentable, allowing both frameworks to coexist while maintaining state sync.

Yes, you need to handle retain cycles when bridging UIKit and SwiftUI. Properly manage retain-cycle safety and sizing within your UIViewRepresentable wrappers to ensure stable memory management and correct layout.