Commentary

Stephen Wellman
 

Isn't It Time Apple And AT&T Opened The iPhone?

Why is the iPhone still a closed shop on AT&T's network? At the time of the launch Apple suggested that it was necessary to keep the device locked, but hinted that the device would be eventually opened. It's four months later and the iPhone is still locked. How much longer must developers wait?

Why is the iPhone still a closed shop on AT&T's network? At the time of the launch Apple suggested that it was necessary to keep the device locked, but hinted that the device would be eventually opened. It's four months later and the iPhone is still locked. How much longer must developers wait?No one really seems to know why AT&T and Apple are keeping the iPhone closed. I have a theory: I think Apple may be more scared of open access than AT&T, assuming such a thing -- a vendor being more scared of open access than a carrier -- is even possible.

One reader on Slashdot chimed in on this earlier today:


More Mobility Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

"Apple's reasoning for keeping the iPhone a closed platform is that they don't want to 'potentially gum up the provider's network'. An article in the New York Times, though, points out that there are hundreds of phones out there working on open platforms that don't seem to be causing network interference. AT&T and Palm, in fact, welcome experimentation on their platforms. In AT&T's case ... on every phone but the iPhone. 'Hackers who have explored the workings of the phone say it uses the frameworks and structures that Apple uses on its other platforms to enable development; it just hasn't been documented. So if Apple is going to allow applications later, is there any reason -- other than vindictiveness or obsessive interest in control -- that it would want to cut off those developed by the pioneers who figured things out ahead of the official launch?'"

Apple claims that it plans to open the iPhone to outside developers. Yet more than four months after launch, programmers are scrambling to access the iPhone and Apple continues to ignore them. What gives?

While hackers open the iPhone and crack almost every lockdown Apple can devise, Apple continues to fight them. What company on earth would ever want to squash the desire of eager developers to make its devices better?

In fact, Apple seems to hate the iPhone hackers. Just this weekend Apple confirmed that new software updates for the iPhone will turn any hacked iPhones into bricks, or iBricks.

I understand why Apple wants to protect the iPhone. The company is proud of the device and its mobile user experience and it wants to protect that experience. But the other champion of mobile UX, the BlackBerry, has a developer program and has warmed to developers in recent years. As a result, the BlackBerry continues its reign as king of the enterprise market and is now exploding with prosumers, too.

If Apple really wants the iPhone to be a mobile programming platform -- and not just an expensive iPod Touch with an overpriced carrier contract -- it needs to be more open. And more important, Apple will need smart, eager developers to help it make the iPhone a serious smartphone platform. C'mon, Mr. Jobs, tear down the iPhone wall.

What do you think? Isn't it time for Apple to open up the iPhone?


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