Apple MacBook Pro Core 2 Duo T7700 2.4GHz 2GB 160GB GeForce Apple MA896LL/A MacBook Pro

Apple MacBook Pro Core 2 Duo T7700 2.4GHz 2GB 160GB GeForce Apple MA896LL/A MacBook Pro.

 

It’s important to get a Macintosh with an Intel chip in order to run Xcode. Some of the older Mac Book Pro’s were not outfitted with this chip and they cannot be used for iPhone development. If you are just starting out, a used mac, from a source like this, is a great place to start.

I’ve been a geeks.com customer for over ten years and they always have some of the best deals on computers. Plus I trust them, they will take things back if they’re not right.

Another option is to go with a mac mini and to connect it to your system’s display and storage. This may get you a faster processor and more memory, still at an affordable price.

Keynotopia

One of the major hurdles in putting the idea into practice is getting the proper user interface. I found it surprisingly complex. In my mind it was easy to get from step A to Step B, but without actually pressing the buttons, etc. you have no idea of what options you might want to have. There are often many branches to the logic, and you need to think about the most effective way to get to C.

I used a product called Keynotopia to create simple clickable PDF files. It’s not perfect but the developer is very active and has updated it at least 3 times recently. It is really easy to pick out the user icons from the Macintosh libraries and create a virtual application, even on a Windows machine, or in PowerPoint or on Mac software. This is a real boon to someone who had to buy a Mac just to get started.

Once yo have your prototype down, it can be the starting point in hiring a programmer to bring the product to life. Explaining your concept to another person is a whole lot easier with visual aids.

Keep a list, journal, notebook, diary, whatever!

I started to realize pretty early on that the flashes of inspiration quickly were forgotten unless I wrote them down. First it was on any scrap of paper, eventually collected into a binder. Now I often write myself and email and then transfer it to a journal. It does help to review these potential applications, because I thik what happens is that a successful developer runs out of creativity just keeping up with the current product. Rereading the ideas helps keep them fresh and in your imagination, hopefully spurring on additional  thoughts or user interfaces.