The suggestions here that engineers are left to write the documentation or that Apple does not care about developer docs are - well, let's just say "wrong".
Apple has (to a close enough approximation) "always" had a Tech Pubs department (see, for example, this interview with Chris Espinosa or this folklore.org article)
NeXT also had a Tech Pubs group.
The documentation is considered part of the product. If you find it to be inaccurate, misleading, or insufficient in any way, you should file bugs. Without feedback, it is impossible to know in what way you consider it to be deficient or how it could be improved. For a long time now it has been easy enough to provide feedback using the form at the bottom of every reference page...
by mmalc — Jan 08
Apple has (to a close enough approximation) "always" had a Tech Pubs department (see, for example, this interview with Chris Espinosa or this folklore.org article)
NeXT also had a Tech Pubs group.
The documentation is considered part of the product. If you find it to be inaccurate, misleading, or insufficient in any way, you should file bugs. Without feedback, it is impossible to know in what way you consider it to be deficient or how it could be improved. For a long time now it has been easy enough to provide feedback using the form at the bottom of every reference page...