My thanks to Sillysoft for sponsoring this week’s DF RSS feed to promote Lux Delux, a Risk-like world domination strategy game for Mac OS X, Windows, and Linux. Lux offers over 700 maps, including fantasy realms and historical scenarios, and has a map editor for building boards of your own. Lux also offers cross-platform network play. There’s even an SDK for programming AI opponents.
And there’s a version for the iPhone and iPod Touch. I’m a sucker for this type of game — I’ve lost a lot of time to both the Mac and iPhone versions of Lux.
One thing that strikes me about Chrome OS and Litl is that neither bother trying to do everything Windows or Mac OS X can do. Not even close. I don’t think either even bothers trying to serve as one’s primary computer.
The idea that they’re designed to serve as secondary computers is a big part of the opportunity I see for new Web-focused OSes. I think that’s one of the implicit factors that define what people call “netbooks”. How many people use one of those as their one and only computer?
If you start with the assumption that a computer will be a secondary machine — something purchased because it’s cheaper, smaller, and lighter — you can make all sorts of different assumptions about what it needs to be capable of.
In the early part of this decade, Apple’s turnaround under Steve Jobs was based on the concept of the Mac as a “digital hub” — a device to which you connect and manage satellite devices like iPods and cameras.1 If you have more than one computer, why should the secondary computer (or computers) need to be just as capable — and just as complex, expensive, power-hungry, and heavy — as your primary one? Why should it run the same OS?
The idea of a computer that does a lot less — leaving out even things you consider essential, because you can still do those things on your other, primary computer — is liberating. That’s the opportunity, and that’s the idea behind Chrome OS and Litl and even Android and iPhone OS.
Long-term, there’s no denying that Google is steering toward a future where typical users have no “primary” computer, but instead where every computer is just a terminal to Web-based software running on servers across the Internet. But there’s an opportunity today for secondary computers that offer just a subset of the functionality of Mac OS X and Windows, especially if they don’t just do less, but (like the iPhone) do less really well. ★
Here’s a YouTube clip of Steve Jobs introducing Apple’s “digital hub” strategy in his January 2001 Macworld Expo keynote. It’s sort of mind-blowing — both in terms of the prescience of the strategy itself and just how long ago it seems. There was no such thing as an iPod yet, Mac OS X 10.0 was still two months away from shipping, and, talking about digital cameras, Jobs mentions that they then accounted for 15 percent of the camera market but would “soon” account for 50 percent. ↩
Alexandre de Rochefort, finance director of French game developer Gameloft:
“We are selling 400 times more games on iPhone than on Android.”
Apologies for the self-link, but I’ve gotten a few questions today from readers asking, honestly, just what the problem is with private APIs. This piece I wrote last year addresses it.
As an addendum, I think there are many developers, especially those who aren’t coming to the iPhone from the Mac, who don’t understand how seriously Apple takes its public APIs. When Apple publishes an official API, it’s a serious commitment that says how something works and will continue to work in the future. Private APIs are subject to change or go away. The idea that something marked private works now so why not use it? is short-sighted. The iPhone OS isn’t just something that Apple has built to last for a couple of years. It’s a platform they’re building to last for the foreseeable future. They don’t want apps in the Store that aren’t future-proof.
Requires a two-year service contract with Verizon, of course, but that’s $50 lower than Verizon’s price. Even cheaper: Dell is selling it for just $120 (again, with a contract), at least in certain areas.
Animated time-lapse map of county-by-county unemployment rates in the U.S. since January 2007. Jarring.
This one seems to be a genuine incorrect rejection for private API use: Juicy Bits has a camera-based app that uses OS 3.1-only camera features, but still runs on OS 3.0 by disabling those features when the app runs on OS 3.0. This particular feature — customizing UIImagePickerController — was frequently abused by private API users in the past, prior to Apple’s introduction of official support for this stuff in OS 3.1.
According to Juicy Bits, they’re not doing that, but their app was rejected anyway:
We’re now wondering if the static analysis tool sees the 3.1.x API call in our app, notices that it runs on 3.0.x devices (that don’t support the new APIs), and flags or rejects it as a result. This would actually make sense! The only problem is that the tool appears to be ignoring the code where we check the device version before making that call, and that may be the nuance that’s causing all of our delays.
Gdgt has a VMware image of the open source Chrome OS version that Google released yesterday. Engadget put together a video showing how to install and use it. If you’re curious to see it in action (as I was), this is far easier than compiling it from source. Hooray for VMware.
But be warned — this release is far behind the version of Chrome that Google actually demoed during their event yesterday. This open source release is missing much of the cool stuff shown yesterday, and only fully works if you have a special google.com account — presumably only available right now to Google employees. You can get more from watching this aforelinked video than by running this image in VMware.
This YouTube video has the demo portion of yesterday’s Chrome OS announcement event. Best tour of the UI I’ve seen.
By the way, if you haven’t seen it before, RogueSheep’s Postage is a very slick iPhone app: it’s a simple little “virtual postcard” app with tons of polish and style.
This is admittedly a little technical. But the gist of it is that RogueSheep sort of got screwed by having their app rejected for this. Their app linked to a version of the Three20 framework that overrode, not called, a private API — i.e. it replaced a private method with its own method of the same name. And Postage, the app, wasn’t even actually calling it. Apple’s tool apparently can’t discern the difference, so developers need to be aware of this or risk automatic rejection.
RogueSheep’s Chris Parrish concludes:
Personally, I’d love to see Apple give us access to the analysis tool to run against our own builds before submission. Or if that’s not possible, perhaps a modification to the review process so this automated analysis happens sooner in the process so we don’t lose so much ground in the now 14-day wait for the review process to complete.
Making the static analysis tool available to developers would indeed be helpful. But I suspect it wouldn’t work in terms of game theory. Honest developers could make good use of having access to the tool, to help ensure their projects are free of private API violations. But dishonest developers would use the tool to figure out ways to slip private API calls past the checker. Parrish’s second request, for Apple to run the tool against submissions far sooner in the review process, strikes me as a good and reasonable one.
Update: Here’s a note from an informed DF reader:
Overriding private methods in a category is far worse than calling them directly.
Everything in your process will get the overridden behavior of the private method and assumptions about side effects go out the window.
One consequence of Apple’s crackdown on the use of private API calls is that some apps are using them, or at least including them in their binaries, without knowing it. One popular open source framework, Joe Hewitt’s Three20 (linked here on DF back in March), played a bit fast and loose with private APIs, and so now there are numerous developers with apps getting flagged for private API calls made from the Three20 framework. This Google Groups thread covers the problem and the work that’s being done to create a branch of Three20 that’s free of private API calls.
(Hewitt, of course, was in the news last week after he quit as lead developer of the Facebook iPhone app citing frustrations with the App Store process. It’s reasonable to wonder whether this had anything to do with Apple’s crackdown on private APIs, because the Three20 framework was originally extracted from the Facebook app. I exchanged a few emails with Hewitt on the matter, and that’s not the case — his frustrations with the App Store process lie elsewhere.)
John Herrman at Gizmodo explains the basic gist of the static analysis tool Apple is now running against App Store submissions, to identify (and reject) apps that use private API calls. Apple has been explicit from the get-go that doing so was a bad idea and reason for rejection, so I think this tool is a good idea, in general. The trick will be making sure it doesn’t generate false positives.
Notice anything about most of the laptops?
The hard part about criticizing the App Store is that it doesn’t fit into a black-and-white narrative. It’s not bad or good. It’s both. In fact, it’s more extreme than that — it’s both amazingly good and horribly bad. And, frustratingly, many of us see how the bad parts could be made better without sacrificing the good parts.
This piece by Paul Graham addresses this dichotomy, and tries to make sense of Apple’s seeming blindness to the App Store’s severe problems:
Actually I suppose Apple has a third misconception: that all the complaints about App Store approvals are not a serious problem. They must hear developers complaining. But partners and suppliers are always complaining. It would be a bad sign if they weren’t; it would mean you were being too easy on them. Meanwhile the iPhone is selling better than ever. So why do they need to fix anything?
Later on, Graham captures what it is that gives me The Fear:
An organization that wins by exercising power starts to lose the ability to win by doing better work.
I wish I’d written that sentence.
Michael Gartenberg:
I used to postulate that Apple had become the Nordstrom for technology retail. Ever shop at Nordstrom’s? If you haven’t, you should just for the experience. In fact, if you run a support organization, you should go to Nordstrom’s and shop for training purposes.
I don’t think Apple is the Nordstrom of technology any more. I just think they’re the new Nordstrom as defined by level of service.
Yeah, but do they dance?
Lots of new stuff in Buzz Andersen’s excellent iPhone Twitter app, including support for Flickr for uploading image attachments and excellent integration of Twitter’s just-released geolocation API.
Lucas Mearian:
Google Inc. said today that the upcoming release of its new Google Chrome operating system will not support products hard disk drives in favor of solid state drives (SSD).
This is smart. First, Chrome doesn’t need large amounts of local storage. Second, going SSD-only lets Google use a file system that is designed from the ground up for random access drives. If you can count on the drive being solid state, you can make all sorts of performance optimizations. They’re building for the future.
Smartest thing I’ve seen so far about Chrome OS is this tweet by Alex Payne:
I have no opinion about Chrome OS. All I know is that cheap hardware feels cheap. It’s less “cloud computing” than “disposable computing”.
Ridiculous. It seems as though they’re not trying to patent sparklines in general, but rather the specific idea of sparklines embedded in a spreadsheet grid, but still.
Here’s Microsoft’s write-up on the feature. Looks great. Excel has always been my favorite app from Microsoft.
Lots of information here about what Chrome OS is going to look like and how it’s going to work. In a nut, it’s an OS that boots in under 10 seconds and gives you a WebKit browser. It does more than a browser, like by recognizing when USB mass storage devices (cameras, Android phones, etc.) are plugged in, but you don’t do things like deal with a local file system or install applications. You turn it on, you use the Web.
(Just like with Chrome the browser, with Chrome OS, “Chromium” designates the open source branch.)
The only options are RealPlayer and Windows Media. In Google’s defense, though, Apple hasn’t bothered to even try live-streaming an event for years.
Mark Pilgrim is killing it with his live-tweet coverage.
Update: VLC-friendly streaming URL.
Nice microscopic imagery.
So the big news so far today is this report in DigiTimes stating that Apple has delayed its tablet from March until “the second half of 2010” because of significant changes to the display components. Keep in mind that Apple has never publicly said a damn thing, not a word, about any new tablet computer, let alone ever stated that it was due in March. This is one of those stories where what they really mean is that Apple has missed a rumored deadline.
But the details of DigiTimes’s report strike me as very odd:
The sources also indicated that in addition to Foxconn Electronics (Hon Hai Precision Industry), Quanta Computer and Pegatron Technology are expected to be manufacturing partners for Apple’s two tablet PC models — one of which will have a 10.6-inch TFT LCD panel while the other will have a 9.7-inch OLED panel.
This makes no sense to me. Why would Apple have two tablet models with entirely different displays that are only one inch different in size? We’re into the third year of the iPhone and there’s still just one single display type and form factor. Apple may well have placed orders for both these types of displays, but I say no way are both for tablet computers.
Requires a two-year contract with Sprint, but still, that’s a big discount off Sprint’s regular price of $150. And, they’ve got the Pixi for just $25.
The NYT:
By the time the Yankees rushed the field to celebrate their 27th World Series victory, Robert Caplin had photographed the action — 12,000 times. The result is a romantic and captivating time-lapse presentation.
Captivating.
A few weeks ago, in a piece here titled “Herd Mentality”, I argued that PC makers who want to succeed should create their own OSes:
It’s not just that Apple is different among computer makers. It’s that Apple is the only one that even can be different, because it’s the only one that has its own OS. Part of the industry-wide herd mentality is an assumption that no one else can make a computer OS — that anyone can make a computer but only Microsoft can make an OS. It should be embarrassing to companies like Dell and Sony, with deep pockets and strong brand names, that they’re stuck selling computers with the same copy of Windows installed as the no-name brands.
Hardware and software both matter, and Apple’s history shows that there’s a good argument to be made for developing integrated hardware and software. But if you asked me which matters more, I wouldn’t hesitate to say software. All things considered I’d much prefer a PC running Mac OS X to a Mac running Windows.
Microsoft, I think we’d all agree, sees things the same way (well, in terms of software being more important). They’ve got PC makers under their thumb.
The most common bit of critical feedback I got in response to “Herd Mentality” is an argument that goes like this: You don’t want a world with several additional desktop OSes. It would make for a compatibility and interoperability nightmare. We were there before, in the early days of the personal computer, and it was a mess.
I say two things to that. First, it may have been a mess, but it was a beautiful mess. It was glorious. It was fun. The Apple II, the IBM PC and DOS, Commodore, Atari, Acorn. The TI-99/4A.
Second, this ain’t then. The world is a very different place today.
In those days, before DOS ran most competing platforms out of the market, interoperability and data interchange were at best difficult, and often impossible. Data was stored in incompatible file formats written to incompatible floppy disks1 by incompatible apps compiled for incompatible CPU architectures. Even later in the ’80s, when networking became common (at least in businesses) the network protocols were proprietary.
That was the world where DOS won out. Get everyone on DOS and you could all open each other’s WordPerfect and 1-2-3 files, if only by sharing them on floppy disks. So DOS gained users, and because it gained users it got developers, and because it gained developers it got more users.
A similar feedback loop is going on with the iPhone today, but it’s far less sticky. The DOS/Windows monopoly grew impregnable because it was a platform where the only way to play along was to join it.
That’s not the way things are today. Sure, there are massive business markets where Windows remains essential. But the Web is a bigger platform than Windows. The Web is universal. Every computer is on the Web. The Web provides us with a core set of software and APIs that work everywhere.
Supposedly, tomorrow Google is set to unveil the details of Chrome OS, but we already know one thing about it: it’s designed around the assumption that the Web is the most important software platform in the world today.
But last week came news of another, similar initiative, from a far smaller company than Google: the Litl — a $700 “webbook”. If you haven’t seen it, go check out their web site — the videos on their support page offer the best introduction to their UI. It’s fascinating and clever in several ways. It is refreshingly simple. And most importantly: it is truly new. I don’t know if Litl is going to be a success — $700 seems steep for this when you can get a MacBook for $999, and the easel mode strikes me as an awkward gimmick without a touchscreen — but everyone involved with the Litl deserves tremendous credit just for having the stones to do this, to say, Hey, maybe computers in 2010 can do better than a user experience that is fundamentally unchanged from the original Macintosh in 1984.
If a small startup can build the Litl, why couldn’t a big company like Dell or Sony? People today still love HP calculators made 30 or even 40 years ago. Has HP made anything this decade that anyone will remember fondly even five years from now? Inkjet printers?
If Palm can create WebOS for pocket-sized computers — replete with an email client, calendaring app, web browser, and SDK — why couldn’t these companies make something equivalent for full-size computers? The hard part of what Palm is doing with WebOS is getting acceptable performance out of a cell phone processor.
These PC makers are lacking in neither financial resources nor opportunity. What they’re lacking is ambition, gumption, and passion for great software and new frontiers. They’re busy dying. ★
If your computer even had a floppy drive, that is. Some, like the TI-99/4A, typically used cassette tapes. Cassette tapes! ↩
Tons of new features and improvements. I’m going to give it a shot as my daily browser.
Nice JavaScript hack.
Dan Frommer:
Recall that Google has the ability to buy Sprint 3G (and Clearwire 4G) services and re-sell them to consumers, via its $500 million investment in Clearwire. Google could play the role of “virtual” network operator, offering smartphone service for much cheaper than a carrier might sell it at retail.
Carl Howe speculates that if Google is going to release their own phone, it’d be unsubsidized and unlocked, able to run on any major carrier’s network. That would still be contrary to what Andy Rubin said last month, and still strikes me as something that would antagonize existing Android handset makers. And you’d still have to pay for a monthly voice and data plan, the cost of which isn’t likely to be any less than the plans for subsidized phones.
But, if this is what Google has in mind, perhaps Google itself would be willing to “subsidize” the cost of the phone to some degree in anticipation of mobile advertising revenue. There’d have to be some sort of hook like that, because a starting price of $400 or $500 just isn’t going to cut it against subsidized iPhones and Droids that start at $99.
If there’s any truth to this Google phone rumor, I think Mike Arrington may be onto something here:
The Google Phone may be a data only, VoIP driven device. And Google may be lining up at least AT&T to provide those data services for the Google Phone, says one person we spoke with today.
The idea is that you’d just pay for a data plan, get a phone number and voice mail through Google Voice, and all your “calls” and SMS would go over IP. Lower monthly bill, no bullshit about minutes. It’s a wonderful idea — I just can’t believe any of the U.S. carriers would go for it.
To watch this video from Microsoft regarding the upcoming IE 9’s support for standards and interoperability, you are prompted to install Silverlight. (Via Mark Pilgrim.)
I’ve started a log of who’s afraid (and not) of the terrorists.
Jon Ronson:
My eight-year-old son, Joel, comes into my office to ask if there’s a worse swearword than fuck. “No,” I say.
There’s a silence. “You’re lying,” he says.
“There’s none worse than fuck,” I say.
Joel narrows his eyes. “I know you’re lying,” he says.
(Ronson made the excellent documentary Stanley Kubrick’s Boxes.)
Mike Arrington says Google is definitely making its own phone, coming in “early 2010”:
Way more interesting are the rumors we’ve been hearing for months about a pure Google-branded phone. Most of our sources have unconfirmed information, which we describe below. But there are a few things we have absolutely confirmed: Google is building their own branded phone that they’ll sell directly and through retailers. They were long planning to have the phone be available by the holidays, but it has now slipped to early 2010. The phone will be produced by a major phone manufacturer but will only have Google branding (Microsoft did the same thing with their first Zunes, which were built by Toshiba).
That puts Arrington on the same side as the almost-always-full-of-shit Scott Moritz. On the other side: Andy Rubin, vice president of engineering for Android at Google, who just two weeks ago said Google would not “compete with its customers” and “We’re not making hardware. We’re enabling other people to build hardware.”
So either Mike Arrington is totally wrong or Andy Rubin is a liar.
At the outset of Google’s Android initiative, I was a proponent of their creating a Google-branded, Google-designed reference handset. But at this point, after promising their hardware partners for 18 months that they wouldn’t do that, I don’t see how Google could do it without infuriating their partners and spoiling their trust. It’d be like what Microsoft did to its PlaysForSure partners when it introduced the Zune.
Now in beta, 280 North’s developer tool for building and designing Cappuccino apps for the web and desktop. Access to the beta program is $20.
This is great:
In an apparent move to band against Tim Langdell’s over aggressive defense of the trademark “EDGE”, a number of indie developers have made announcements today that their games will incorporate the EDGE name.
Anthony Ha for VentureBeat:
Microsoft’s chief software architect Ray Ozzie weighed in at Microsoft’s Professional Developers Conference today on the battle between different smartphone platforms (including Windows Mobile). It’s not the applications available on the different platforms that will be the differentiators, Ozzie said, even though that’s what many companies and writers seem to focus on.
“All the apps that count will be ported to every one of them,” he said. It’s a completely different situation from the PC market, where software’s built to run on a Windows or a Mac, he said. Mobile apps require very little development, so it’s much easier to bring them onto every platform.
Stupid and wrong, but what else is he going to say? There’s nothing truthful or accurate he could say about mobile development that looks good for Microsoft. If I were at Microsoft, I’d say their best bet should be to start arguing that mobile web apps are the future of mobile development, rather than native apps. That might actually be true, and it actually gives them a chance — if they were either able to produce a WebKit-caliber mobile browser or willing simply to adopt WebKit themselves. A big if, but at least that’s possible.
Good question raised by Guy English: Why is it OK for the new Star Wars: Trench Run iPhone game to include this image of an iPhone, when many other apps, like for example Instapaper, have been rejected for including original icon artwork that merely resembles an iPhone?
Jiminy.
Terrific WSJ interview with Cormac McCarthy:
WSJ: How does that ticking clock affect your work? Does it make you want to write more shorter pieces, or to cap things with a large, all-encompassing work?
CM: I’m not interested in writing short stories. Anything that doesn’t take years of your life and drive you to suicide hardly seems worth doing.
Joe Wilcox published a piece Friday titled “Apple was NOT more profitable selling cell phones than Nokia in Q3” (caps emphasis his). It’s in reference to the widely-cited (and linked from DF here) report last week by Strategy Analytics which concluded that Apple generated more profits than Nokia from mobile phone handset sales last quarter.
Wilcox was skeptical — nothing wrong with that — and conducted his own investigation into the numbers:
Well, hell, that sounds reasonable enough, right? Wrong. Apple and Nokia SEC filings tell a different story. Both companies announced third calendar quarter results a few days apart in mid October. For devices and services, Nokia reported profits of €785 million, which is about US $1.1 billion. Apple reported total profits — that is for all products — of $1.67 billion in its earnings press release, and later the 10-K filing. I searched the 10-K, and, as I expected, Apple doesn’t breakout iPhone profits.
But it doesn’t have to for purposes of this discussion. I don’t doubt that Apple is more profitable per handset, since iPhone is a smartphone, than Nokia. But the numbers don’t add up to Apple’s overall handset profitability exceeding Nokia’s during third quarter, unless someone is making the bold assumption that all, or nearly all, Apple profits came from iPhone. They surely do not. What? Apple made only $700,000 on iPod, Macintosh, retail and software — $1.6 billion — on iPhone. No way.
The disturbing lack of fact checking seems to be a trend when it comes to Apple these days.
This is disturbing. Either Joe Wilcox has uncovered a massive, widely-reported error, or, he has made a fool out of himself. (That Wilcox thinks $1.67 billion - 1.6 billion is $700,000, rather than $70,000,000, offers a clue.)
What Wilcox is arguing is that Apple only reported $1.67 billion in total profit for the quarter, so how could they possibly have made $1.6 billion from the iPhone alone? But that’s not what Apple reported at all. Perhaps if Wilcox had actually read more than just the first paragraph of Apple’s press release announcing the company’s earnings, he’d understand. Apple’s announcement stated:
Apple today announced financial results for its fiscal 2009 fourth quarter ended September 26, 2009. The Company posted revenue of $9.87 billion and a net quarterly profit of $1.67 billion, or $1.82 per diluted share. These results compare to revenue of $7.9 billion and net quarterly profit of $1.14 billion, or $1.26 per diluted share, in the year-ago quarter. Gross margin was 36.6 percent, up from 34.7 percent in the year-ago quarter. International sales accounted for 46 percent of the quarter’s revenue.
In accordance with the subscription accounting treatment required by GAAP, the Company recognizes revenue and cost of goods sold for iPhone and Apple TV over their estimated economic lives. Adjusting GAAP sales and product costs to eliminate the impact of subscription accounting, the corresponding non-GAAP measures for the quarter are $12.25 billion of “Adjusted Sales” and $2.85 billion of “Adjusted Net Income.”
As everyone who follows Apple should be aware, Apple is accounting for iPhone sales over eight quarters. This practice is unusual, but it’s not complicated. This is how they’re able to give software updates to iPhone owners free of charge, and, conversely, because iPod sales are not accounted for on a subscription basis, why iPod Touch users must pay for the same updates. When Apple sold an iPhone last quarter it only accounted for one-eighth of the revenue and profits for that quarter. The remaining seven-eigths will be accounted for over the next seven quarters.
Subscription-based accounting does not mean that Apple doesn’t pocket the cash from iPhones all at once. They do — at least since June 2008 when they switched to the model of being paid an up-front subsidy from the carriers, rather than the per-month revenue-sharing model they used with AT&T for the first year. It’s all just a matter of accounting. What Apple calls “non-GAAP measures” are its way of saying “this is how much money we actually made this quarter”. The “adjusted net income” of $2.85 billion is effectively what Apple would have reported as profit for the quarter if they weren’t using subscription based accounting for the iPhone and Apple TV.
This is how Apple’s cash on hand has grown by $21 billion in the last three years, from $14.5B on 30 September 2006 to $36.2B on 26 September 2009. (Click “Balance Sheet” and “Annual Data”.)1
It is true that Apple does not specifically break out the revenue or profits from iPhone sales. But unless you think Apple is selling a lot more Apple TVs than most of us do, it’s pretty safe to say that the iPhone accounts for nearly all of the difference between Apple’s GAAP and non-GAAP reported profit, which difference came to $1.18 billion for the quarter. That suggests Strategy Analytics’s numbers are in the ballpark. It’s also worth noting that Nokia does not account for its handset sales as Apple does — Nokia accounts for them “normally”, up front, in the quarter in which they were sold.
Even if Strategy Analytics’s $1.6 billion figure is a little high, they’d have to be wrong by over $500 million for their overall conclusion (that Apple made more profit than Nokia selling phones) to be wrong. Here’s another back-of-the-envelope calculation. Apple does release the total number of iPhones sold during each quarter. Last quarter it was 7.4 million. So take Strategy Analytics’s estimate of $1.6 billion in profit, divide by 7.4 million iPhones, and you get $216 in profit per iPhone, which, again, sounds like it’s in the ballpark. (Unsubsidized 16 and 32 GB iPhone 3GS models — the most popular iPhones — sell for $599 and $699 respectively, and Apple’s reported gross margin for the quarter was 36.6 percent.)
As for Wilcox’s would-be exposé, I’m almost embarrassed to quote his concluding paragraph:
As for Apple’s overall phone profits being higher than Nokia’s, don’t believe it. Just because dozens of Websites report something as true doesn’t make it so. Because of the extent of misreporting, I can’t say where the fault lies. The Strategic Analytics report, which again I haven’t seen, might have gone no further than present numbers showing that Apple makes more profit per phone than Nokia. That absolutely makes sense. But to assert that iPhone generated $1.6 billion profit during a quarter when all Apple products generated $1.67 billion is simple stupidity.
Simple stupidity indeed.
If you subscribe to the Market Share gospel, it’s perhaps very hard to wrap your head around the idea that a company with 2.5 percent unit sale market share generates more profit than a company with 35 percent market share. But the numbers aren’t complicated. The iPhone really is that big a deal. ★
That Wilcox is so utterly befuddled by Apple’s iPhone accounting — convinced that Apple is generating far less cash than they actually are — makes me wonder how many analysts and investors are likewise confused about this. Probably many. So it’s worth noting that a recent accounting rule change may change the way Apple reports these numbers in the near future, such that Apple could report revenue from iPhones the way casual observers expect — in the quarter the sales occurred. Here’s what Henry Blodget wrote about the rule change in September:
The new rule will allow Apple to recognize the iPhone hardware revenue and profit at the point of sale, while an estimated value for the software will be recognized over the life of the device.
A change in accounting shouldn’t make a difference, but I’m guessing it will. Look for Apple’s stock to jump up if they make this change. ↩