Commentary

Apple To iPhone Developers: It's 3.0 Or FAIL

Apple recently informed developers for the iPhone platform that from here forward, all new applications submitted to Apple must support iPhone OS 3.0. If they don't, the apps will be rejected.

Apple recently informed developers for the iPhone platform that from here forward, all new applications submitted to Apple must support iPhone OS 3.0. If they don't, the apps will be rejected.Hmmm, this sets the stage for some interesting changes. In an email to developers, Apple said:

Beginning today, all submissions to the App Store will be reviewed on the latest beta of iPhone OS 3.0. If your app submission is not compatible with iPhone OS 3.0, it will not be approved.

Existing apps in the App Store should already run on iPhone OS 3.0 without modification, but you should test your existing apps with iPhone OS 3.0 to ensure there are no compatibility issues. After iPhone OS 3.0 becomes available to customers, any app that is incompatible with iPhone OS 3.0 may be removed from the App Store.

It is no surprise that Apple wants to be sure the new OS is supported, but to force all apps onto the 3.0 standard could leave some end users in the cold.

More Mobility Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

We have to assume that OS 3.0 will be backward compatible with apps developed for iPhone firmware 2.2.1, at least in the short term. Of course, with all that iPhone 3.0 brings to the table, I don't know why any end users would choose not to update.

I've been using iPhone OS 3.0 Beta for about a month, and have yet to run into any incompatibility issues with respect to the apps I have installed on my device.


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