“In May 2007, I interviewed Steve Jobs on the subject of native apps for the iPhone months before the new phone first went on sale,” Daniel Eran Dilger writes for AppleInsider. “Six years later, his answers are now haunting Google’s rival Android platform because the search giant has failed to heed the advice leaking from the top of Apple’s ship.”
“Certain parties have since rewritten the history of the App Store to tell a very different story: one where Steve Jobs was opposed to the very idea of native apps. This version of events maintains that Apple didn’t have any plans for an App Store until the jailbreak community (and perhaps some early Android hobbyists) demonstrated how great apps could be, forcing Apple to reluctantly open its own app store in response,” Dilger writes. “Jobs didn’t set out to simply stop native iPhone development out of ignorance of its potential. I know that because I asked Jobs about it at the company’s 2007 shareholder meeting, amplified at the microphone in front of the assembled news media tasked with covering the event. When I asked ‘does Apple recognize the needs of large, institutional buyers who are excited about the prospect of applying low cost, handheld computers with their own custom development?’ Jobs clearly replied that Apple was aware of the demands of third party developers, but that the company was also still working on how to balance the needs for secure software and deployment. It was a work in progress.”
Dilger writes, “In October , Jobs came out with one of his rare public blog entries where he stated, ‘Let me just say it: We want native third party applications on the iPhone, and we plan to have an SDK in developers’ hands in February. We are excited about creating a vibrant third party developer community around the iPhone and enabling hundreds of new applications for our users. With our revolutionary multi-touch interface, powerful hardware and advanced software architecture, we believe we have created the best mobile platform ever for developers.’ Jobs’ next comments, in retrospect, sound eerily prophetic: ‘It will take until February to release an SDK because we’re trying to do two diametrically opposed things at once—provide an advanced and open platform to developers while at the same time protect iPhone users from viruses, malware, privacy attacks, etc. This is no easy task. Some claim that viruses and malware are not a problem on mobile phones—this is simply not true. There have been serious viruses on other mobile phones already, including some that silently spread from phone to phone over the cell network. As our phones become more powerful, these malicious programs will become more dangerous. And since the iPhone is the most advanced phone ever, it will be a highly visible target.'”
Much more in the full article here.