wants me to mention the Cocoa Touch framework. He feels that its excellence is an important factor in the success of native iPhone apps.
Point is, although Gruber’s probably right, he ought to be wrong.">
I have several more things to say in the Web apps vs. native apps debate, and I’ve decided that a few smaller posts treating just one subject would be the best form. Today we kick off with the Cocoa Touch framework.
John Gruber wants me to mention the Cocoa Touch framework. He feels that its excellence is an important factor in the success of native iPhone apps.
Point is, although Gruber’s probably right, he ought to be wrong.
If all you have is a hammer, every problem becomes a nail. If all you know is the Cocoa Touch framework, every app you make will become a native iPhone one, whether that’s a good idea or not.
If you have to choose between, whatever, two kinds of Web servers, picking the one with the better tools (libraries and such) is an excellent idea. They’re both Web servers, after all. The net result to your end users will be the same, but your job will become easier.
It’s different with Web apps vs. native apps.
The net result of a Web app is that anyone with a modern browser can use it, though on some devices the user experience is less-than optimal. The net result of a native app is a superior experience on the iPhone, and nothing for the rest of the world.
What do your users want you to pick, superior user experience or vastly bigger reach? Do you need device APIs, and is there a way to get paid? Those are the questions that matter right now.
Cocoa Touch is excellent. There, I said it — without having the faintest idea what I’m talking about, obviously.
But it’s just a tool. It shouldn’t matter.
If you like this blog, why not donate a little bit of money to help me pay my bills?
Comments are closed.