Nick commented on my earlier post claiming that the cost of a development machine (a Mac) is simply too much to sway him to develop for the iPhone. This mentality ignores the principle that good apps on the iPhone MAKE money.
CONNECTED DATA writes about why they develop for the iPhone:
When the pitcher releases the ball a batter has to decide where they will swing. If they wait too long the ball will be in the catcherâ€™s mitt before they decide. The same logic is why we are developing for the iPhone.
In learning about development for the Blackberry platforms, we have to create a build for each phone and each network. As a developer, I just canâ€™t afford it. Most of my customers right now have Blackberries. I think that in the next year or two they will have an iPhone.
Thing is, this problem already exists for Symbian devices and it will become an issue for Android devices as well. (It’s less of an issue for Windows Mobile because the UI is so generic ,and meaning that in the negative sense, that it doesn’t matter. It would be on a refrigerator and still be crap!)
David Pogue’s recent and damning review of the new BlackBerry Storm has the internet all a-twitter about the shortcomings of the device.
“A light touch highlights the key but doesnâ€™t type anything. Only by clicking fully do you produce a typed letter. Itâ€™s way, way too much work, like using a manual typewriter.”
“Remember: To convert seconds into BlackBerry time, multiply by seven.”
“Freezes, abrupt reboots, nonresponsive controls, cosmetic glitches. Way too much ‘unexpected behavior.â€
Developers arenâ€™t a tricky breed. They like to code cool applications and get paid for it. The benefit of coding for the iPhone/iPod Touch is that the specs are the same and arenâ€™t likely to change anytime soon. Coding across platforms takes more time, energy and money, and if the payoff isnâ€™t there, then developers arenâ€™t likely to adjust their code for the varying screensizes and hardware/software features specific to a particular phone.
Mark my words – it’s simple to develop for Android now that there’s a single hardware specification (in the form of the T-Mobile G1). It’ll be entirely different when there’s five competing hardware manufacturers.