[yreg]

This makes sense in a company with limited. Apple can obviously both care about customer UX and have a good development documentation, have a good public bug tracker, pay out bug bounties, etc.

If they hire 20 people for this and give them a few offices in their precious mothership, it won't affect customer UX in the slightest. They may continue to give it the top-most priority, which is the right choice to make.

That's why it's unclear to me. Apple's valuation is a poor argument. It could have been even higher, since there are areas where Apple is failing precisely thanks to poor developer relations. E.g. serious gaming on Macs/Apple TV, even though the hardware is amazing.

[ChuckNorris89]

Why are you asking me? Why not ask Apple directly?

Their valuation and product success is poof that they're on the right track as a company. The fact that you think their track should be different just to make you happy is irrelevant to them and is exactly what Jobs answered in 1997 to that irate developer: The consumer product matters more than pleasing devs which are niche and picky group of people that are hard to please anyway and not really relevant as their consumer target.

I'm gonna have to stop the conversation here since we're going around in circles at this point.

[yreg]

Overall financial results are no proof that making a bad documentation was the right decision. I don't even believe it's an intentional decision, probably just carelessness.

>Why are you asking me? Why not ask Apple directly?

Not sure what's this supposed to mean, you are the one who decided to reply.

>The consumer product matters more than pleasing devs

This is obviously a false dilemma which I already pointed out. I never ever said that pleasing the devs should be prioritized over the consumers.