After many months of waiting, jailbreaking, and crying ourselves to sleep mode, the iPhone SDK is finally upon us! Having the ability to write apps for our iPhones with the very own tools and SDK that Apple itself used would make writing apps for the iPhone so much easier, right? Well, maybe not... As most of us know, some of the great things about Jailbreaking was the ability to use AIM, MSN, Gtalk, and having it run as a background process as you do other things on your iPhone. You could go do something in Safari, change a song, watch a video, or something else and still receive IMs in the background. With the new SDK, your apps are now limited to what they can do, making it so they can not run as a background process. This means that if you want to change a song while you're using AIM, you have to sign out, change your song, then sign back in. Now, there are workarounds for this, but since that would violate the iPhone Interface Guidelines, it would be forbidden from being put on the AppStore.
Another limitation to the new SDK includes the "you can't make plugins using other APIs than our own" rule, which would stop any Safari plugins in it's tracks such as Java or a 3rd party flash, as well as stopping any sort of emulator for the iPhone from being created.
Is this fair of Apple? Maybe or maybe not. Hopefully in future releases and revisions of the SDK and documentation, they'll be more flexible on what we can and can't do.
