Just wanted to let the two of you that are following this blog that we've handed over the code for the open source code for the Field Guide to our beta tester. We are moving ever closer to the date that you can get your hands on the code.
Why are we beta testing? In getting the code ready to release, I've simplified the code in some areas but also added in a new setting or two. While I know you're a fan of Museum Victoria's particular shade of green, it's remotely possible that somebody with a less sophisticated palette may want to change the colour of the toolbars. A charming shade of mauve may be their choice, or perhaps honeysuckle, if they're up with this year's Pantone colour. The setting for this was buried in a class, but is now set in a configuration file.
Even if I hadnt tweaked the code, it's important to check that the whole thing isn't going to fall in a heap when you get the code and run it yourself.
At the risk of teaching you to suck eggs, after adding your own data to the code, you should put aside a block of time do some extensive testing of the app before releasing it to the public.
Before releasing our field guide, we checked the detail page of each animal, made sure the images were there, maps were appearing, that audio was working and there weren't any unexpected crashes (not that we had a list of expected crashes). I'm not going to lie to you, while the images and audio in the guide are beautiful, it can get a little tedious having to go through a couple of hundred in one sitting.
It's unlikely, but possible, that something in the data for one of your animals will interact strangely with the code. Better to find that out before you publish to the App Store.