Commentary

Marin Perez
 

The iPhone's Push App Service Appears

While iPhone owners may never get true background applications, the seeds are in place for the next best thing. Select developers are saying the 2.1 version of the firmware has an API for Apple's Push Notification Service.

While iPhone owners may never get true background applications, the seeds are in place for the next best thing. Select developers are saying the 2.1 version of the firmware has an API for Apple's Push Notification Service.According to MacRumors, Apple sent the following note to select developers with this message:

This is the second beta of the iPhone SDK targeting iPhone OS 2.1, including bug fixes to iPhone OS as well as an early implementation of the Apple Push Notification Service API. This API is not yet integrated with a live push server.

Apple decided not to allow background apps because they believe it would quickly bog down the phone's processor and eat away at the battery. The company's solution would be its Push Notification Service, which would send all of these applications' transmissions through an Apple server.


More Mobility Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Through this, applications will be able to push alerts to the phone through an Apple server, which has a persistent background connection. The company didn't say when the 2.1 firmware will be released, but the push service is slated to roll out in September.

Apple has a decent argument -- as multiple running apps can make many smartphones nearly unusable -- and this is an elegant solution. But you still have to miss a true background instant messaging or streaming radio application. I liked Alexander Wolfe's suggestion of issuing certifications for certain apps to run in the background.

More than that, I wish Apple could trust and empower iPhone users and developers by giving up just a bit of control. Of course, it wouldn't be Apple if it did.


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