iPhone Development Postmortem


The big day has come and gone and we have many more details regarding the iPhone Development Program. Much of what I discussed in the previous post regarding enterprise support has been adopted by Apple, though only the privileged few that were allowed into the enterprise beta program know the full details (and I am not one of them). It does appear that the iPhone will take its place beside BlackBerry devices and Windows Mobile phones in bathroom stalls across the globe, though Apple still has a long way to go in terms of winning the hearts and minds of corporate finance & architecture committees.

The main problem: there are a large number of applications, ranging from SAP to SalesForce.com that work fine on existing mobile platforms. If they didn’t work well, organizations wouldn’t be using them. While the iPhone may be great for future adoption, the ROI will be a bit difficult to justify if businesses want to bring them in to replace existing solutions, even if vendors create iPhone-specific versions of the programs. Do you really need an iPhone to run that ACME CRM application? I can speak from direct enterprise experience, however, that even non-techies were watching Apple’s announcement since the integration folks at my company received at least five calls immediately afterwards with the same questions: “So, when are we enabling support for my iPhone?”.

Developers Wanted?

Unfortunately, the enterprise features may be the most positive message coming from the announcement, at least initially. While over 100,000 budding iPhone developers took Steve Jobs seriously and gave up their precious personal information to download the SDK, many – including this friendly neighborhood blogger – were ultimately very disappointed to learn that Apple was not interested in our $99.00USD and that they should go read a book…or something. Anything, really except to expect their cool apps to be running on an actual iPhone, rather than an emulator.

I can understand Apple needing to slowly roll out memberships, at least initially, but their “thanks, but not right now” e-mails were taken pretty hard – and justifiably so – by very real and talented developers (as opposed to hobbyists like me). Apple needed to do a much better job communicating the rules of the game before soliciting participation and they should have just tagged their “A-list” candidates separately before pseudo-opening program to all.

I have and can still develop applications for BlackBerry devices, Windows Mobile and even the Sharp Zaurus. I paid nothing for that privilege and spent no money on development kits or membership. I realize Apple makes its own rules and that the iPhone is a vastly different device but why open the floodgates only to let a few drops of water out (or in, as it were)? I doubt this will dissuade budding iPhone coders, but it has definitely stunted the fervor of some of Apple’s more influential indie allies.

No Limits?

If the developer exclusivity is the first shoe to drop, the other is the limitations expressed in the SDK around what you can or cannot do with the device. While other blogs have commented on some specifics, I’m still not comfortable enough with Apple’s legal department when it comes to relating details from documents Apple has expressly forbidden disclosure of. Suffice it to say, certain applications will require a great deal of creativity in order to work the way developers wish (don’t expect SMS-like notifications of chats or tweets).

Developers have also expressed concern regarding the double-edged sword that is iPhone application distribution model. While some are thrilled to have their applications presented via the iTunes store front, others are concerned that there would be no support for try-before-you-buy offerings or allowing of add-on modules post-install (via direct download, either free or purchased). Further more, augmenting applications with small scripts/actions may be forbidden as well.

Hope Lies With 2.0?

Unlike programming for “real” computers (Macs or Windows PCs), coding for mobile platforms with actual limitations on processing speed, memory and storage space requires different ways of thinking. It will be challenging enough making decent applications without Apple’s current restrictive climate. Hopefully, we will start seeing further details about wider-scale participation in the program as we get closer to the magical summer release of iPhone software version 2.0.



@ Patrick

All of the third party software titles will be downloaded through iTunes. All recipient iPhones of each software offering will be known. If there is an important patch posted to the App Store; the next time each of those iPhones logs in to iTunes for synching, they will be prompted to download the upgrade.

Apple has gotten updates to software right. Not only to they get it right the first time for the most part, but also any addditional functionality that Apple wants to build out in future upgrades are rolled out with automatic software updating technology. I’m quite confident that Apple will makes this technology available to all software that is sold through the AppStore.

Apple will likely limit or discourage buggy software, even in initial release versions. Since the number of hardware devices is limited, it ought not be difficult to debug the software and be confident that good functional software on 1 device ought to work well on the entire platform. But any developer who subsequently wants to offer a free update or even a paid add-on module ought to be able to target their particular installed base quite precisely through the AppStore.

The AppStore will be a revolution in how software will be distributed going forward. I can imagine that Apple will eventually bring some of the AppStore innovation back to the mac platform in time.


You said “…others are concerned that there would be no support for try-before-you-buy offerings or allowing of add-on modules post-install…”.

I think the real problem developers have is that they can’t issue a patch easily. This upsets the whole “throw a release out there and patch it if there’s a problem” paradigm we’ve been in these last 20 years.

John Ryan

…folks at my company received at least five calls immediately afterwards with the same questions: “So, when are we enabling support for my iPhone?”.

The reason for business enterprises to support the iPhone is because their employees want to use, and will be using iPhones. After all, it is the people of a company that are productive, not the application/device.

Comments are closed.