<![CDATA[Gizmodo: push notification]]> http://tags.gizmodo.com/assets/base/img/thumbs140x140/gizmodo.com.png <![CDATA[Gizmodo: push notification]]> http://gizmodo.com/tag/pushnotification http://gizmodo.com/tag/pushnotification <![CDATA[Rumor: iPhone 3.0 Might Let Apps Run in the Background for Real Multitasking]]> Something significant has obviously delayed the original September launch of push notifications, Apple's solution to not allowing apps to run in the background. MacRumors hears that Apple is considering allowing real background processes instead.

Android and especially the Pre have made background apps and the true multitasking they allow look a lot sexier, and the iPhone's one-app-at-a-time paradigm more restrictive, even with the innovative compromise of push notifications.

Push notifications, for the uninitiated, would allow apps like AIM to send you notifications (through Apple) of say, new IMs via an SMS-like prompt, even while the application isn't running. So you could kind of think of the app as running in the cloud, essentially. Not multitasking by any means, but for some an acceptable compromise on battery-draining background apps.

MacRumors says that if what they're hearing is true, and Apple allows apps to run in the background, it would happen with the iPhone 3.0 software. On the current iPhones, it would likely be restricted to one or two processes at a time, but with the beefier hardware of the next-gen iPhone, it'd be less restricted.

Having apps actually run in the background might actually be worth the longer wait. [MacRumors]

]]>
http://gizmodo.com/index.php?op=postcommentfeed&postId=5145303&view=rss&microfeed=true
<![CDATA[Why Is Apple iPhone Push Notification Still Missing?]]>

The latest iPhone 2.2 operating system fixes many things, but something is still missing: Push notification services. Once again, Apple has missed the opportunity to enable push notification in a new update, which is specially bad after they failed to meet their self-imposed September deadline. That makes it almost two months late now. So what's the problem? Is the cause just a technical glitch or maybe there are other hidden, last-minute reasons behind it?

Many developers and users were eagerly awaiting for the 2.2 update to finally enable push notification services, which disappeared from the 2.1 beta right before release. Essentially, push notification is a clever way for your iPhone applications to receive messages from the network at all times, even while they are not active. Since the applications don't need to be active constantly, asking data to the application server every X minutes, this method saves power while giving you all the convenience of server-sided push messages.

As any BlackBerry user knows, push services allow the developer to implement functionality that is extremely useful. For example: An instant messenger program would be able to notify you whenever a new message is received, even while the application itself is not running. Think about it just like an SMS. Another example: A voice over IP application can receive a call and alert you right away, so you can pick it up like any normal telephone call. Or maybe return the call using the normal telephony service if you are not in a Wi-Fi spot.

As you can imagine, this makes push notification a Holy Grail for users and developers alike. The only people who may not be happy about these are the carriers. After all, the idea of an instant messaging application with push notification services taking over their lucrative SMS business doesn't seem like a very good one.

Or maybe I should take off my tin foil hat and just assume that Apple has hit a roadblock that nobody at engineering ever expected. But a two month delay? Why? It just sounds too weird.

Whatever it is, I only hope they deliver it as soon as possible.

]]>
http://gizmodo.com/index.php?op=postcommentfeed&postId=5098887&view=rss&microfeed=true