These are exciting times! As an assignment at school, we are writing an iPhone game. It's a simple number guessing game. You know how it goes... Generate a random number, get the user's guess at the number, tell them "too high" or "too low." When the user guesses it right, you tell them how many guesses it took. It's actually one of the most boring games you can play, but it's a great beginning for learning a framework (and in the iPhone's case, a language, too). It has all the great aspects of a first app: input from the user, output to the user, and simple processing with a nice added bonus of learning how to randomly generate a number. I worked hard to do things right. I wanted it to rotate properly, stay centered, respond well to all input, the usual goals. I wanted a market worthy app, even though it'll never make it to the App Store or the Android Marketplace. All the specifications my teacher inparted on us for the iPhone app, I continued to uphold for my own Android project. I'm going to do my best to explain my experiences with both platforms. I have the same experience with both of them. About a month ago I wrote a Hello World app for each of them. School got in the way of looking into either of them deeper, until this assignment. I may seem pre-determined to be better at Android considering my Java history, but I'm accounting for it by saying that I haven't worked in java for years and that I'm currently getting three hours a week being taught iPhone dev and Obj-C. It evens out enough for me! This article will not be as much a walkthrough as it will be a comparison between my two experiences.
More...
Advice, Android, Case Study, Development, iPhone
iphone, android, xcode, eclipse, interface builder, game