Why Apple Doesn't Blog - Vaporware 91
DECS writes "If anyone is still wondering why Apple does not encourage its internal developers to maintain blogs, Roughly Drafted is carrying an example of how the good intentions behind sharing information can result in unpleasant, unintended consequences." From the article: "As customers, we all want to know what's going to happen in the future, but we will also turn around and beat developers with the very information they share with us. One of the terms we hit them with is, of course, vaporware. The other thing about blogs is that written text fails to capture the full range of rich human communication. It's easy to take more offense than is necessary to the wrong choice of words. Minor and casual criticism can quickly ferment into a difficult stink, and attempts to burry it can often just make it worse. Blog entries are like emails that cc: to the entire world."
Instead of asking... (Score:5, Insightful)
So what would be the answer? "Because everybody is doing it!". "because I want to know what they are up to!". "I love Apple and I want to get constant news and articles about Apple!". Well, none of those are a valid reason for blogs, really.
Five minutes of my life back please (Score:5, Insightful)
Enough with links to blogs of people who - in Wikipedia terms - are not notable.
They do it to keep selling end of line products (Score:4, Insightful)
I'm not sure this is still a wise thing to do when they are entering new markets, as the much rumoured iPhone would do (if it exists). I need a new phone, but I'm holding off until Macworld San Franciso because of the rumours, rather than being tied in to a 12 or 18 month deal on a cometitor's product - which must be good for Apple if the rumours are true, and better if they publically said "we will ship an iPhone soon", as more people would wait.
Re:Instead of asking... (Score:3, Insightful)
-- Brian Boyko
-- Professional Blogger.
Re:Don't know about that (Score:3, Insightful)
Not necessarily. That just means no one actually ever filed suit. But potential lawsuits are not typically reported by the media unless one side or the other makes public statements about the legal threat (or there was a leak).
Hypothetical: Acme Widgets Corp. buys a SA license in 2001. Microsoft doesn't Vista deliver until late 2006. Someone at Acme notices and gets angry about it in 2004 or 2005 perhaps. They threaten to sue Microsoft. Microsoft then may make some sort of concessions to Acme Widgets Corp. Discounts on Office 2003 or Windows 2003 Server, free support for an additional year on one or more products, and maybe even cash incentives. So Acme Widgets never goes public with its plans, satisfied that it got something out of the bargain. You get the picture, I'm sure.
one way vs. two way street (Score:5, Insightful)
Re:Apple (Score:3, Insightful)
Author's comments...ugh. (Score:3, Insightful)
Just STFU already!
Daniel Eran, RDM | Homepage | 12.08.06 - 8:48 am | #
This in response to a lengthy comment posted with plenty of meat to it as a counterpoint. This is the author's way of defending his article?
This should be filed under "Stick-Your-Tongue-Out-And-Scream-Until-The-Other
Re:A hint (Score:3, Insightful)
I think the GP was referring to consumer devices like the iPod and consumer macs. If you only count the retail home market, Apple is one of the top brands by marketshare for computers as well.
Blogging is, at best, a mixed bag for product dev. (Score:3, Insightful)
First, if your product developers blog, they may be giving your competition advanced notice of what you are up to much sooner than you otherwise might.
Second, the bloggers do not necessarily represent the average user. In fact, in my experience those that read and respond to blogs often have widely divergent needs from the targeted customer. If your responders are largely hard-core geeks, say, they may be pushing for more advanced features instead of what the other 90% of your customers most want (e.g., usability). Advanced feature requests are rarely appropriate for a product at an early stage of development and that time is generally better spent on more fundamental issues.
Third, what someone asks for and what they actually most need as a real world customer are often very different. Having been involved in product development, it has been my experience that most people can't articulate what they most want. They often do not understand, for instance, that the current products out there are horendously and unnecessarily hard to use. Even if they "feel" frustrated with usability, they can rarely identify what frustrates them exactly, let alone propose a better way to solve it. Often times their requests actually hamper what they need (e.g., add this feature as the expense of greatly increasing UI complexity).
Lastly, I believe you can actually increase negative publicity about your product by blogging. If your blog readers are heavily exposed to your product and expect that their suggestions will be taken seriously, you have to also remember that they may represent the bulk of the first users when you launch. They may take for granted what you have already accomplished and their expectations may be out of line with what you can or will deliver. Instead what you may get for your troubles is negative publicity coming from a bunch of people that really don't represent your target base and yet these same people might serve to steer a good number of your target customers away.
I'll admit that I didn't RTFA. However, I would argue that Apple and companies like them are perhaps the best arguments not to blog. I would assert that their products are far more focused on usability (and ultimately their customers) and have tended to be far better recieved on a marginal basis than any of their competitors. If you were to read many of the modern blogs on, say, the ipod and other portable players you would get the impression that customers prefer anything but and that they really want a ton more features. In practice, most people still prefer the latest iterations of the ipod and I would argue that apple's marginal efforts are still better directed than most...
Blogging probably makes sense sometimes (depending on: the stage of development, user base, type of product, etc) but I also think there are many where it is very much counter-productive. You might argue that management might simply, say, ignore certain input, but this kind of input can also serve as a distraction for your developers and may be bad for morale.
Re:Counting paragraphs until the first MS bash (Score:4, Insightful)
Seriously, you sound like somebody watching the Daily Show saying, OMG, I know that Jon Stewart is going to make some comment about Bush... THERE, THERE IT IS!!!
As for Digg: it exists to tell weak-minded people what they already think they know. More than 80% of it is now PR fluff and other inoffensive written-for-digg articles that say nothing, and are commented on by people like yourself, who add nothing to the conversation apart from hypocrisy, impune bad motives without any proof, and generally suck.
So go roll in Digg and leave the bits of the web that are not yet as stupid alone.
Re:Author's comments...ugh. (Score:2, Insightful)
Also, it's nearly impossible to figure out whether it's a Daniel Eran posting or not. A lot of your "legit" comments sound exactly like those "fake" comments--insulting and condescending. Like this one in response to VGPowerlord below:
"So go roll in Digg and leave the bits of the web that are not yet as stupid alone."