Software developer Dylan Schiemann used Steve Jobs' own words against him in a presentation on developing third-party software applications for Apple's iPhone.
"You can write amazing Web 2.0 and Ajax apps that look and behave exactly like apps on the iPhone," CEO Jobs said at an Apple Worldwide Developers Conference in June in San Francisco.
"It depends on your meaning of the word 'exactly,'" Schiemann said Monday at the AjaxWorld 2007 Conference & Expo in nearby Santa Clara.
Jobs says Apple will allow third-party software developers to write applications to run on an iPhone, but not be installed on it. Instead, the apps can only be delivered through the device's Safari web browser. While an endorsement of Ajax from Steve Jobs is welcome, Schiemann and others at the Ajax conference say there are limitations on how their apps can run on Safari, and there is a vibrant community of developers writing apps to install directly on iPhone, contrary to Apple's wishes.
Schiemann's iPhone has 40 applications running on it, including the ones Apple ships from the factory, but also some unauthorised apps installed directly on the device. Christopher Allen, another AjaxWorld presenter who runs the website iPhoneWebDev.com, has 50 apps on his iPhone, including several unauthorised ones.
The Ajax conference, held Sept. 23 to 26 and drawing about 900 people, devoted five breakout sessions to developing iPhone apps using Ajax, a development tool for writing Web-based applications.
Schiemann, CEO of web-based applications developer SitePen, promoted the Dojo Foundation's open source Dojo Toolkit for writing iPhone applications but says even it can't overcome all the limitations in trying to work with the current iPhone version of mobile Safari. Notably, he said, web-based apps can't react to the iPhone's signature feature, which is the ability of a person to use finger-touch commands, such as the "pinch" to zoom in on a web page.
Allen adds: "When the user pinches, the web-based application is not notified that the end user is doing that . . . because the web browser does not tell them."
Allen makes a distinction between hackers who add software apps and those who break into the iPhone to avoid using AT&T's wireless service. Jobs says Apple will take action to prevent unlocking.
Asked for comment for this story, an Apple spokeswoman emailed a company statement that seems to make no such distinction: "Apple strongly discourages users from installing unauthorised unlocking programs on their iPhones. Users who make unauthorised modifications to the software . . . violate their iPhone software license agreement and void their warranty."
Apple did not reply to attempts to clarify the statement.
Schiemann argues that his adding apps to his iPhone does not constitute "unlocking" it, so he doesn't consider that a violation of the terms of service. "It is, after all, still my iPhone."
The developers hope that Apple improves support for developers and fixes other glitches when it introduces an updated version of Safari, expected in October, and when its long-delayed Leopard operating system is released.
Still, Schiemann and Allen understand why Apple is being protective of its platform. If someone installs an unauthorised application and it breaks some other part of the iPhone, a customer will blame Apple, not the developer. If an iPhone software upgrade somehow disables an unauthorised app, Apple can't have to worry about apps it doesn't support in the first place.
Despite the frustrations, the iPhone app market is worth pursuing, both men say. Given the robustness of the iPhone experience, its expansion into markets abroad and Apple's sales forecast of 10 million units, it is a significant opportunity.
"This is a gold rush, but we're basically in the alchemy stage where we're trying to turn lead into gold," Schiemann says. "We're trying to do all these things with the device because it's so freaking fun to use."