If so, yeah AppKit has some warts, and it isn’t all that well documented. That’s how it’s been since I got started with it back in the early-mid 2000s, where your best sources for learning were random blog posts or books (the latter of which I couldn’t afford as a teenager).
If you ever do iOS dev, UIKit is a lot nicer to use in almost every way. It’s been polished and modernized a great deal in comparison, and because iOS as a platform is so much more popular/important it’s throughly documented end to end.
Still, AppKit does have some advantages, like its batteries-included nature which allows one to build complex apps with few or no third party dependencies.
100% SwiftUI! As a new Apple developer, I wanted to use their latest and greatest. It does get restrictive sometimes, but compared to having to dive into AppKit/UIKit hackity-hack SwiftUI solutions here and there are a lesser evil IMO.
Ahh yeah, SwiftUI isn’t fully baked yet unfortunately, particularly on macOS. I’m just now starting to use it in significant capacities in iOS projects and haven’t yet started on Mac because of that.
If so, yeah AppKit has some warts, and it isn’t all that well documented. That’s how it’s been since I got started with it back in the early-mid 2000s, where your best sources for learning were random blog posts or books (the latter of which I couldn’t afford as a teenager).
If you ever do iOS dev, UIKit is a lot nicer to use in almost every way. It’s been polished and modernized a great deal in comparison, and because iOS as a platform is so much more popular/important it’s throughly documented end to end.
Still, AppKit does have some advantages, like its batteries-included nature which allows one to build complex apps with few or no third party dependencies.