If you haven’t heard already, Apple this past Thursday had just announced their software roadmap for the iPhone (and iPod Touch). If you haven’t seen the event, follow this link to go watch it. If you don’t want to watch the hour long presentation, or if software development details sound boring, a summary of what I want to discuss can be found here.

So what does the release of the SDK mean? Well for me and other current iPhone users, we will soon have an official method for developing and using 3rd party software. Previously, the only way a user could use 3rd party software on their iPhone was if they performed a “jailbreak” on their phone. In a nutshell, this is an unofficial way for users of the iPhone to gain access to run applications not created by Apple directly on their phone. This was in response to Apple’s request that all iPhone applications be created for the iPhone’s web browser in the form of web apps. Web apps were limited because they essentially did not have access to any specific iPhone functions such as the accelerometer, and even basic things such as read and write access to the iPhone itself. Additionally, it required that the iPhone have some form of internet access (cellular or wi-fi). Sometimes both might not be available, such as when you are on a plane, in a hospital etc. With the SDK, developers are allowed access to do all of this and more.

What’s most exciting about the SDK though is what developers discovered about making applications for the iPhone. As a prior user of a T-Mobile Sidekick (which runs Danger’s proprietary OS, has its own SDK and application delivery store, similar to Apple’s, but a closed and heavily protected architecture), and a Windows Mobile Smartphone (a completely open architecture, developers distribute the software themselves), Apple is not alone in terms of software development on a mobile device. What’s different about developing about the iPhone, compared to say a Blackberry or a Windows Mobile phone? It’s all about the operating system and the development environment given to you. From what I’ve seen during the keynote this past week, and the types of software that companies have developed and demoed, I am very excited. Unlike most other mobile phones, the architecture of the iPhone allows for a much more robust development environment that is much more similar to a computer desktop operating system than a mobile phone operating system. Because the difference between the iPhone and desktop like computing is blurring, the scope of development will follow.

Imagine the ease of use of a fully integrated Flickr application on the iPhone. The ability to take photos from the camera, upload them to Flickr, tag your photo with the multi-touch interface, or even edit and crop the photos within the iPhone itself without going to your computer. Or how about a version of Delicious Library for your iPhone that leverages the camera and intuitive interface to help you catalog your growing collection of physical music, movies, and books. How about games? A few games were shown during the event this past week, so this will obviously be a huge focus for developers. By having the ability to directly develop games for the iPhone, we will start to see much more engaging forms of gaming. Should the Sony’s and the Nintendo’s of the world be scared… I think so, why you ask? Let’s not forget that the iPhone has one thing both the PSP and the Nintendo DS don’t have. An always on internet connection through your wireless provider. They all have a wi-fi card, but you’re not always in range of a wi-fi access point. Can you say networked gaming on the iPhone?! Not only networked gaming, but can you imagine a Second Life client for the iPhone? Technically it might not be possible to run it all the time with the speed of the cellular data connection in the 1st generation iPhone, but I won’t completely rule the possibility out.

4 Responses to “iPhone as a Software Platform”

  1. nonny Says:

    I want to learn more. Hopefully, some of this will get covered in our mobile module…

    If you’re excited, then I’m excited.

  2. Otto Says:

    Check out these links regarding iPhone ‘open SDK’ limitations:

    TechCrunch, March 7 08 — includes the SDK documentation.

    iPhone SIM (Un)locking from Ryan Block


  3. Hey Otto, I think those are all valid points, but right now we’re at the wait and see mode. I was particularly concerned about the one application running at a time restriction. But this makes sense from a User Interface perspective… I used a Windows Mobile phone before and you can do anything on that OS. I also found it very cumbersome to actually exit out of most applications on a Windows Mobile phone. I had to bring up the task manager and select the Processes that were unnecessary or no longer needed, then select end task to completely exit the Application. Otherwise I’d start to notice that my phone became less responsive and did not work as well. Apple put the restriction to keep only one app running at a time, I’m guessing, to lessen the confusion on how to exit a program, and to keep the iPhone’s resources properly managed for a smoother user experience. But I’m sure if the application needs it, they will adjust the restrictions and guidelines appropriately as the user’s needs change over time.

  4. Otto Says:

    Lots of positive comments about the iPhone SDK here at eComm 2008. And did you see that VC Kleiner Perkins has committed $100 million for iPhone app development? This makes Google’s pledge of $10 million for Android look paltry. (A worthwhile side note: the VC funding is moving to mobile)

    Looks like the obstacles from Techcrunch and others are not show stoppers, as you seemed to be saying.


Leave a Reply