The Secret Reason Why Android Will Support Intel Chips
When I first heard about Andy Rubin announcing Android will be optimized for Intel Atom chips for all versions of Android from now on, I was very disappointed with Google, because I thought it was a poor strategic decision on their part. It felt backwards. Even Microsoft is moving to ARM, and I bet Apple will make a Transformer-like clamshell or at least a Macbook Air-like one based on ARM, soon, too. So why would Google support “the past”, instead of looking forward ?
Why ARM Is Winning
ARM chips keep advancing fast, at about 2.5x improvement each year, or about 4x every 18 months. That’s twice as fast as Moore’s Law for x86 chips. And best of all, they advance that much, while still keeping the same overall low power consumption. And I bet that’s all chip makers’ goal – to improve their chip as much as they can, every year, while maintaining the same power consumption.
What this means is that ARM chips are closing the performance gap on Intel/AMD chips fast, and chips like Kal-El should already feel like they are more than enough performance wise, for most people, whether it’s on a phone, or even on a tablet. With a Kal-El chip, page rendering of complex and “full” web pages should happen in about half a second, and it will feel almost instant. Games will look great, too, and it’s one of the reasons I’ve been wanting Google to transform Google TV in a “console platform”, with set-top boxes based on Kal-El or other such powerful quad core chips.
Plus, the ARM competition is fierce compared to the x86 market, where you only have 2 competitors: Intel and AMD. In the ARM market, you have the 4 main ones: Nvidia, Qualcomm, TI, and of course Samsung. But then you also have Freescale (their quad core 1 Ghz Cortex A9 might be in PS Vita), ST-Ericsson, Marvell, and soon LG (they licensed Cortex A15 from ARM recently).
That’s 8 competitors! What more could Google want in terms of chip competition? Why would they still need Intel to provide competition, when they’re still stumbling and crashing in the mobile market with their Atom CPU?
Google and Intel’s Inadequate Partnerships
My first guess was that this decision was mostly political. I mean, Paul Otellini, Intel’s CEO, is on Google’s board for crying out loud. Then they have strong relationships in the server market, since Google build their own servers, and obviously they have strong ties with Intel there, since they’re probably their biggest customer.
They’ve also partnered on Google TV, which I still think was a huge mistake on Google’s part. It’s the main reason why Google TV failed. Well, Logitech’s set top box costing $300 was the main reason, but Intel had a big part in that. Their Atom CE, should cost somewhere between $75-$100, as a component. That translates to about $150-$200 from the retail price. If you’ve been watching iFixit’s disassembling of phones and tablets, you’ll see the components end up about half the retail price. Meanwhile, a Tegra 2 costs about $20, so with it, the Logitech Revue would cost about $150 at most.
Then, Google partnered with Intel again on Chromebooks – and again the pricing seemed significantly more than people expected. Granted, people were comparing the dual core 1.8 Ghz Atom with a single core older 1.6 Ghz Atom in cheaper netbooks, but I believe they were ultimately right. The Chromebooks are too expensive for what they are supposed to do – just browse the web. It’s irrelevant if it even comes with a quad core i7 in them. People are not going to pay hundreds more for that, when it’s still only for browsing the web.
That’s the main mistake Motorola and HTC did with their tablets, too. The $500 price is about the maximum people are willing to pay for such a consumption device, regardless of how many “specs” you throw in there.
So why didn’t Google go with ARM, and make them $200-$250? That would’ve been the sweet-spot for Chromebooks, instead of $350-$500. They’ve said they will, so hopefully we’ll see some $250 Kal-El based Chromebooks, soon. But it was still a mistake to start out like that, and get negative reviews on it as first impressions. They might affect their growth in the future.
I’m really hoping this is not another one of such mistakes by partnering again with Intel, because if Google actually helps Intel get a hold of the mobile market, they’ll be hurting themselves rather than helping themselves in the end. Here’s why.
Why Microsoft Wants Intel “Back”
Why does Microsoft go to ARM now? They are very vulnerable there, starting from scratch with no apps. They are much behind even Android on tablets with Windows 8 for ARM. Android already has at least hundreds of tablet optimized apps, and they already have the 200,000 or so mobile apps, where most can still be scaled up pretty nicely on a tablet.
The reason is because Microsoft thinks Intel can’t pull it off. Not only do they think Intel won’t achieve the kind of performance/power consumption/price that ARM chips have (or they’ll do it too late), but they also think they won’t be well received by the market, even if they do. It wouldn’t be the first time when even a big player from another market, was rejected by a new market. So they don’t want to bet their farm on Intel.
But here’s the thing. Microsoft would love for Intel to become a strong player in the mobile market, because then they can start promoting Intel-based tablets again, where their real strength lies (with x86 legacy programs). So if Google actually helps Intel become a strong player in the mobile market through Android, Google would barely benefit from it, since like I said, chip competition is very strong already in the mobile market, but Microsoft would benefit a lot more.
So is there more to this than just a political decision meant to help Intel, but with little benefit to Google? I believe there may be and hopefully I’m right, because I would hate for Google to make such a bad strategic decision, otherwise.
Android, Your Main OS Everywhere
Here’s what I think is the real reason why Google may be optimizing Android for Intel’s chips: Google wants to become your main OS, not just on smartphones and tablets, but also on all older and newer x86 systems.
If that’s the real reason, then it may not be such a bad decision after all, and in fact it’s pretty smart. As Android becomes a more mature and even more popular OS, you will be able to do more and more with it, and once you get more professional applications, you’ll want as much performance as possible, too. It will take a while until ARM reaches Intel’s most powerful chips (even though it seems Intel has all but stopped improving the performance of the Ivy Bridge CPU, and they want to focus more on lowering power consumption), and Google may not want to wait until that happens.
Plus, with so many hundreds of millions, if not billions of PC’s out there in the world, Google may want to make it easy for Android to be installed on those machines one day soon. Of course, it’s not just Intel chips they’d have to worry about if they want to make that happen, but it would be one huge obstacle cleared out of the way. Now that Intel has Google’s ear, AMD will probably ask Google to optimize Android for AMD chips, as well, and in return, Google may also ask them to support Android on other older machines of theirs.
So ideally, Google would get both Intel and AMD to make drivers for Android for their other older chips, while “pretending” to help them get a hold of the mobile market, with no significant outcome that would favor Intel or AMD. That would be the best case scenario for Google, without compromising themselves much in the mobile market, and without leaving the door open for Microsoft.
What do you guys think? Did Google do the right thing partnering with Intel on this, or should they have stayed exclusively with ARM and let Intel fade away in the “PC world” and hurting Microsoft in the same time, while they move on with the “Post-PC world”?