Monday, November 30, 2009
I found a VERY useful post at
This provides in great detail how to establish a static library which can then be linked into your applications. Any routine that will be used in more than one application should be in a static library.
In addition my daughter will often have a specific set of 8 sight words to learn for that week. She needs to learn those for this weeks test, but we also need to go over the older sight words so that she continues to gain mastery over them.
There are multiple sight word applications in the store, but most of them suffer from limitations that I can bypass.
Exiting Limitations on many sight word applications
- A lot of the applications only support 100 or fewer of the sight words, divided into groups, and which have to be purchased separately.
- The applications only allow you to use the pregenerated sight words.
- The ability to limit the words you go over to a specific set is not present, or is not easy to use.
The following are the features of the sight words application I would like to develop.
Minimum Feature List (in priority order)
- It should include all of the common sight words, both from the Dolch and Fry sight word lists with out of the box spoken versions of all those words.
- It should support the ability to add additional words to the list.
- It should support the ability to record your own version of the words using the iPhone.
- It should support the ability to create and manage sub lists of the total word set.
Additional nice to have features
- The ability to designate individual words to be successfully identified or not, and to remove the successfully identified ones from the current pool.
- The ability to change fonts and colors.
- The ability to restore the DB back to its original state.
- Games where a word is pronounced and select a sight word from individual choices. The faster the word is selected the higher the score.
- Better graphics and colors
Thursday, July 30, 2009
A helpful tip from
Namely that if you are going to be selling applications, you should submit your contract information as soon as possible so that once you have you application approved, you won't be waiting for Apple legal to review it.
Sunday, July 19, 2009
5/15/2009 I bought into the developer program.
5/19/2009 I sent an inquiry about why they haven't sent me the activation code.
5/28/2009 I sent another email
6/23/2009 They responded to the first email, over a month later, and resent the email that had never been sent
7/7/2009 They responded to the second email that I had successfully enrolled in the program.
The moral of the story is that if you are going to join, join soon, and if you don't get an activation code rapidly, send a support email because it will take over a month for them to respond to the email.
Monday, June 8, 2009
Seeing the success of the application store, I've decided to try to write some software for the iphone, and maybe even make a little money along the way. This blog is for my products (when they come out), as well as my general experiences with iphone development.