Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

hakr100

macrumors 6502a
Original poster
Mar 1, 2011
967
113
East Coast
...and just about everyone else's these days is that no companies seem willing to make the investment in having serious documentation written.

I've got IOS 7 on my iPhone 5, and I've had a lot of questions, some of which were answered clearly and completely here, for which I am thankful.

But Apple's user manuals (the IOS 7 one for the iPad and iPod are up on its site already) don't cover a third of the sorts of questions that arise, and there are no charts showing the various connections between its software, its operating system and its devices. You pretty much have to guess much of the time what impact a particular toggle has in another area. I've been using iPhones, iMacs, and Macbooks for a long time, and I find this is true throughout the product line.

In the 1980s, I wrote documentation for a major manufacturer of desktop printers, and that documentation and much of the documentation I saw for other products, was complete. Not 100% complete, because no documentation ever is, but it was at least 75% complete. Today's documentation for high-tech personal devices is no more than a third complete, I would say. To find answers, you have to jump through hoops in many places.

Documentation for the third-party apps sold on the App Store is even worse, or, worse than worse, non-existent.

Vendors assume too much knowledge of product intricacies on the part of their customers.

A plague on their houses. :p
 
Last edited:
It's true, I thought I knew a reasonable amount, but I learned today I'd completely missed a Siri feature allowing you to teach him / her how to accurately pronouce contact names etc.

There'll be loads more I'm unaware of despite having been using iOS 7 for a while now.
 
If you write documentation it becomes bugs not features
/End sarcasm

IMHO real problem is Apple end to end process is extremely poor.

Just taking the tail end of the process for the recent point update of OSX (10.8.5)
- (Testing) External disks now put to sleep whatever option is chosen in Preferences, but there are theories that it is now determined by setting for the display sleep, was this intended, did the testing team catch the difference between behaviour and options proffered,...
- (Documentation) No real release notes - was this sleep behaviour intended? Certainly wasn't announced. If it was then intended then this is poor analysis and use case design
- (Release Management) Feedback site didn't (as of yesterday) allow you to tag OSX feedback with version that was released week earlier, so you either leave it undetermined or set to incorrect version
- and so on
 
No, the main problems are the dumb GUIs since Lion, and not caring about long term support.
 
The Windows 3.1 user's guide was HUGE. It has to be sitting somewhere in this house still.

It's really hard to write documentation for always changing software. And the development teams can be just one or two people as the norm now. So writing a manual is more time consuming than drawing arrows and doing a quick start guide.

Funnily enough, most of my iPad apps DO have manuals.
 
I typically find the contrary to be true. Apple has a huge knowledge base (KB) filled with support documents for their products.

True though, it would be nice to have a regular old manual to read sometimes.
 
One major problem right now is the lack of focus on OS X. I love iOS 7, but I hope they focus on an overhaul of OS X next year.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.