[windpower]

I was recently contracted to help with a (very small!) Mac app written in SwiftUI where they had hit a hard wall on implementing a couple fundamental UI features and needed that part of the UI rewritten in AppKit. "That part of the UI" is about 80% of the surface area of the apps' main window. (Worth noting that the app current deploys to macOS 12, so even the latest deployment target isn't good enough to get us there.)

AppKit may go away eventually, but _today_ it's still required to write a good Mac app even if you can use SwiftUI for large portions.

My experience on this project has also taught me that AppKit can be made to play quite nicely with SwiftUI. The AppKit code is encapsulated well, and from the outside gets instantiated and included exactly as if it were a SwiftUI component.

[jamil7]

This essentially mirrors my experience however the codebase is more around 50-50 split AppKit / SwiftUI, most controls we tend to use AppKit and layout and display SwiftUI. I don't actually think the integration is too painful, layout can be a little weird sometimes where the two worlds awkwardly join but you can work around most issues there.