Possible Scenario for "No Background Processes" VoIP Problem With iPhone

In my previous post, I pointed out the problems of using VoIP on the iPhone as a secondary phone at home. The application would be severely limited for incoming calls because of the "no applications running in the background" rule. If someone calls my VoIP, my iPhone won't "ring" unless only the VoIP program running on my iPhone (will it run in sleep mode?). That is not a feasible solution. One possible scenario is that the VoIP software running on a computer in my home sends a text message to my iPhone saying so and so at this number is trying to call, please launch the VoIP app. Although, by the time the text message arrives, the person would probably have hung up. However, the phone number would still be there.

A better solution would involve Apple adding notifications between a home computer and an iPhone. So in this scenario, the VoIP program is running on my computer and notifies iTunes a call is coming in. iTunes, in turn, notifies my iPhone, and my iPhone asks if I want to launch the associated VoIP app. These types of notifications are not possible yet, but something that Apple could easily implement. Notifications could be expanded for email alerts, iChat messages, and even severe weather alerts.

iPhone SDK: Programs Won't Run in the Background

Silicon Alley Insider and others are throwing a little cold water on the iPhone SDK by pointing out a very important limitation of the SDK:

"Only one iPhone application can run at a time, and third-party applications never run in the background. This means that when users switch to another application, answer the phone, or check their email, the application they were using quits. (p. 16)"

That is really bad news. That means my dream VoIP scenario of receiving calls at home won't work because I'd always have to launch the program and keep it open while at home--too much of a bother.

Read. Silicon Alley Insider.
Read. TechCrunch.

VoIP on the iPhone

One nugget from the SDK launch that may have flown under your radar is when Steve Jobs said that Apple will allow VoIP apps on the iPhone, but only using WiFi. I am very excited about this, as I get poor cell reception in my apartment. I can instead rely on my trusty WiFi signal for phone calls at home. Imagine being able to answer calls, both VoIP and cellular, using just one device, my iPhone. This SDK is a game changer because of how it ties into the combination of superior hardware and OS of the iPhone, something that even Google's Android can't hope to offer (they don't control the hardware) or compete with in terms of overall quality and user experience.

*Update* I guess it didn't slip "under the radar." It made it to the front page of Digg.

Early SDK Access Means iPhone Apps at Launch

A few developers are getting early access to the SDK, according to sources who spoke with Electronista.

"A handful of companies are said to be getting rough versions of the tools to help code more advanced applications than would be possible with the current web-only solution. Exact details of what the kit allows are unknown, though it is confirmed that it produces native programs and somewhat resembles Google's OpenSocial in that it mediates between the programmer and the iPhone operating system."

Having a few apps to look at and buy during the February unveiling of the SDK will give iPhone users and the press something concrete to examine while waiting for the post-SDK wave of apps to arrive. It will also help Apple test out its system for selling the apps and for maintaining the security of the iPhone. One thing is for sure, the first apps had better not only be slick, but extremely useful, especially in light of Apple's failure so far to add user-relevant functionality to the phone. Of course, I have no problem with the iPhone as is.

SDK Quick Thought

Apple has a phone but won't have an SDK for a couple of months. Google doesn't have a phone but has an SDK. So really, it won't be until next summer until both are on level playing fields. What it may come down to is who attracts more and better developers. I hate to quote Steve Ballmer, but it's the developers, developers, developers.

A great core system is built by the giants like Microsoft, Apple, and Google. But the diversity--the catering to the long tail--is done by the developers.

4 Months Until SDK and Then What?

Assuming Apple releases the SDK at the end of the month of February, as is their way nowadays, it could be much longer before we see a large number of apps on iTunes. Apple will have to hire new employees and build infrastructure to test out these apps. It's likely they are using the time until the release to build that infrastructure. I'll wager that is the reason for the long wait, not the SDK , which is probably mostly finished.

It also wouldn't surprise me that they have already given a rough version of the SDK to a few select vendors who will have apps ready for sale come the public release of the SDK.