iPad Version Update

The first version of the iPad application was rejected by the reviewers at Apple. It seems that they are real sticklers for making sure that the software conforms to their recommended Human Interface guidelines. although the original app “worked” the use of popovers and navigation bars was convoluted. the new version took a lot of time and money to rewrite, but I believe it is a better product for it.

Hopefully Apple will agree and this version will be approved.


Website Work

As I’ve said, the actual programming of the application is only a small part of the work. Developing an application web site to assist in Sales, Updates and a forum or at least a FAQ page is another part.

I have been curious about WordPress for some time, and I had worked in PHP for another “client”, so I decided to add this to my task list. It’s not too bad, and the newer themes do have all of the requirements to make the site “responsive”,  meaning that no mater what device you use to access the site, the screen layout and organization will be optimized for that device. Most of the work is done is the CSS file, but the PHP files do some of the heaving lifting as well

Getting closer to launch

My programmers in India are making great progress. After I pointed out some deficiencies in their project management. they assigned my project to #5 ( I guess the higher the number the longer you’ve been there?) and now they test and provide updates that work.

They fixed the bugs from the iPhone version, and I paid them a down payment for the iPad version. This really got them working, since they now see a stream of income, rather than the large labor loss they took on getting the first iPhone version out that worked. It took something like 12 releases and it wasn’t until after I pointed in them in the right direction did they get the proper database and image matching straightened out.

I don’t think I could have helped them had I not tried to start learning Xcode and iOS programming before I sun contracted out the work. Remember, though that I did take the low bid leader, and I guess you get what you pay for. Overall I’m very happy because the amount I paid was less than or equal to some courses I could have paid for.

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.


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.