
DaringFireball points out an interesting bit of information from the iPhone SDK documentation that could have implications on the effectiveness of a native AIM chatting client
From my brief research this does not appear to be an artificial limit placed on "3rd party applications" vs Apple applications, however. It appears that all applications are also subject to this limitation. Which simply means that only one "app" runs at one time on the iPhone. Now, Apple appears to get around this limitation in ways -- allowing music to be played in the background and also certain alerts to appear (such as SMS) -- but these may be based on special OS X services (not full apps) running in the background.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. Its important to make sure that users do not experience any negative effects because of this reality. In other words, users should not feel that leaving your iPhone application and returning to it later is any more difficult than switching among applications on a computer.
But what does this mean for an application like AIM or iChat where you want to be always available? I'm not sure. Off hand, I'd say a small time developer might not be able to accomplish a true ever-present AIM client, but Apple may have some ways to work around this, at least for a developer as big as AOL.
Article Link