Wednesday, February 18th, 2009
Developing and Releasing My First iPhone App: Part 2 - Availability of the iPhone SDK
Once the availability of the iPhone SDK hit the streets I have been very interested observer. I still don’t actually own an iPhone (just yet), but I did receive an 8GB iPod Touch for Christmas. The iPod Touch is basically an iPhone without the phone. It supports nearly all the same apps and as a development platform, matches the iPhone specs. I am surprised at how often I use my iPod for things that I always wished I could use other phones for.
- Internet access – check
- Simple interface – check
- Useful embedded apps – check
- Ability to store and access music, videos and podcasts – check
This little thing has really become an indispensable part of my life and I while I’m perfectly happy with Verizon as a carrier I am strongly debating dumping them for a new plan for my wife and I. She couldn’t care less about having an iPhone, but there are lots of free phones she would be perfectly happy with so I’m not worried about the cost of switching. On the other hand, the two-year contractual agreement with the added stipulation of carrying a data plan for those two years is a significant consideration these days, especially with the current pace of technology churn in mobile electronics. Still, I really do feel that I would use the data plan. Oh yeah, I said that before too. See a pattern here?
What I haven’t attempted to discuss which is no less important and certainly shouldn’t be discounted is the argument that there are still other viable options available for mobile application development; namely, the G1 and Android. Java-based platform…nice, deep Google integration with geolocation services…very nice, open platform…very very nice, platform adoption rate…hmm we’ll have to get back with you on that.
I did read over the weekend that the Android Store was open for developers to begin publishing apps. That’s certainly a good sign. To wit, Microsoft is going to offer a similar service for WinMo apps as well. For me, at least, it’s a situation where I need to pick my poison as it were. While it would be nice to have the option, I really can’t justify the purchase of an unlocked development G1 phone from Google for $499. The ability to write Java is a powerful incentive since I’m going to need to become an Objective-C / Cocoa Touch ninja which I feel is quite achievable, but within what timeframe? I am certain I could crank out Java-based apps quicker, but I guess the anecdote “if it were easy anyone could do it” is true. When you consider that, as of EOY 2008, Apple has sold roughly 4 million iPhones. Next, how many of those are software developers or have the skills to enter the market; smaller number. Next how many of those developers either have a Mac or are willing to burden the cost of the hardware to enter the market; much smaller number, I’d argue. Next, how many of those Mac owners are application developers either experienced with or want to learn Objective-C; significantly smaller number, certainly. Next, how many of those developers are even interested in developing for the iPhone; smaller number yet. Get the picture? The vast majority of iPhone users are perfectly happy with using the iPhone to make and take calls and the total pool of talent for the iPhone development is quite small by comparison. When you plot that against the number of Java developers, the simple economics of supply and demand make a strong argument in favor of the iPhone. I for one hope to capitalize on my investment in learning by earning a few dollars on my application. If I do that’s great. If I don’t I’ll still be happy that I can choose to work on an alternative development platform if I choose to. Seriously, it’s C and I know C very well. To me, it’s a win-win. I can always do Java just like 3-5 million other developers.
