Developing for the iPhone: The Fear
daringfireball.net
daringfireball.net
He's wrong. The Mail app would be near and dear to Jobs because he wants to take over the market of Blackberry and similar devices also. Keeping a web browser open in order to receive mail pushed real-time from an Exchange server would be extremely awkward.
I find this argument appealing because if Apple took it seriously, it would lead to a more open development process. Unfortunately, I'm not sure the logic is sound -- innovative or important applications aren't necessarily big, so the development cost of one needn't be much more than any other application. If innovative applications are more the product of chance and insight than long development cycles, Apple only needs to attract many developers, not big developers.
However, if you assume the logic is correct, then Android may end up helping the iPhone: If a developer has an idea for the iPhone that requires significant investment, they can develop it first for Android for some payoff, then (with development costs largely sunk) they can port to the iPhone. The net result is that the iPhone would get a large, innovative application that it wouldn't have gotten had Android not existed.
Along those lines, I think we'll quickly see the most popular iPhone applications either ported to Android by their original authors or cloned outright by others.