Commentary

Thomas Claburn
 

Google v. Apple

The future of the Internet may come down to a battle between Google and Apple. It's tempting to see the contest as open versus closed, but that fight -- Google v. Microsoft -- has more or less been decided. Open won. It's hard to see how Microsoft's decision to copy Google's business model can be spun any other way.

The future of the Internet may come down to a battle between Google and Apple. It's tempting to see the contest as open versus closed, but that fight -- Google v. Microsoft -- has more or less been decided. Open won. It's hard to see how Microsoft's decision to copy Google's business model can be spun any other way.Certainly Google v. Microsoft also is a case of free v. expensive, but Google's ad-supported approach can't easily be separated from its embrace of open source development and open information access.

In the case of Google and Apple, the contrast isn't as sharp. Apple's Mac OS X is based on open source Unix. Its Safari Web browser is powered by the open source WebKit browser engine. Apple remains open enough to avoid the kind of government scrutiny that ultimately hobbled Microsoft.


More Internet Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

In the late '90s, Microsoft focused more on cutting off Netscape's air supply than it did on innovating. Apple, meanwhile, focused on products that take people's breath away. The genius of Steve Jobs is that he saw how interface and product design could serve as barriers to entry (and exit). By making great, user-friendly products, Apple has achieved lock-in through customer loyalty.

Apple customers aren't really all that bothered by the iTunes Store toll booth. It works, and that's more than can be said of a lot of online music stores. Apple's iPhone customers will probably react the same way to the iPhone App Store.

Jobs isn't so shortsighted or greedy as to go for complete control. iTunes isn't essential to buy music. There's a way around iTunes' anti-copying scheme. And if you really want, you can use a hacked iPhone. But it's not easy. And the mass market tends to follow the path of least resistance.

Google made search on the Internet easy and effective, and users flocked to it. It wants to do the same thing on mobile phones.

Apple may have something to say about this. Google is a guest on the iPhone and it may not always be welcome.

A recent Market Watch report describes how Google CEO Eric Schmidt, while serving as a member of Apple's board of directors, has had to excuse himself from Apple board meetings on several occasions due to Google's involvement in the Android open source mobile phone stack. Android phones, when they appear later this year, will compete with Apple's iPhone.

At present, there are few signs of friction. Google and Apple get along well, a friendship strengthened by mutual distrust of Microsoft. But several years down the road, Apple is likely to find itself in Microsoft's position: trying to sustain its walled-off, profitable, and very pleasant iPhone eco-system in the face of unruly innovation driven by Android developers.

Google's path to victory lies in transforming the telecom industry by bringing prices down and loosening the death-grip of mobile telcos. It wins by turning the phone into an open mobile computer.

The problem Google faces is that its mobile industry partners are more comfortable with Apple's vision of a moderated computing environment. The popularity of the iPhone proves that walled gardens, if well-tended, can be nice places to live with plenty of revenue opportunities.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links