I have the same issue -- Apple developer documentation, at least what you find on Google, is really awful. Sometimes I even have to watch youtube videos of random developers to figure out how objects' protocols are supposed to work. Developing for Apple is really a huge pain unless you're immersed in that environment.
It’s one of the reasons I abandoned a v2 of my app that was doing low-key quite well in the store. A handful of daily paid app downloads for 0 marketing. I eventually hit a bug in core data in the v2 that drove me to insanity as the docs just didn’t cover what I needed and nothing online helped. I’ve come back as I can see I will eventually burn out in the JS world and SwiftUI is legitimately great (so far for simple stuff) but I know one day I’m going to be in the same spot again - I just take HackingWithSwift as the docs at this point
Apple doesn't care about developer experience. Hardware/software dev at Apple is basically that strong/weak doge meme.
The hardware dev is pushing up against the boundaries of what is possible to manufacture, and they do it with shrinking time scales each cycle.
Apple software gets shittier and harder to develop every year. Some of the stuff I understand, like the onslaught of permissions when everyone upgraded to Catalina. Others like the state of XCode baffle me.
It gets harder and more expensive to target Apple platforms every cycle, no matter how much better the hardware gets.
historically apple's docs were and are pretty awful... apple's docs are going through a transition period right now and it looks like they are breaking backwards compatibility perhaps
