In the previous two installments of this series, we labored through some ornery hardware wrangling and tested our mettle with some serious Objective-C coding, now it's time to deliver our app to the masses.
This journey began on February 25 with the assembly of an Apple iPhone app dev system and culminated with my first app published in the Apple iTunes App Store on March 22. By all accounts, this turnaround time could have been reduced by six days had I not foolishly deleted a CAF audio file from the official app submission bundle. The good folks at Apple spotted this glaring omission and duly informed me on March 16 that I should fix the bundle and then resubmit the whole shebang. I immediately complied, but my gaffe delayed the app approval process for an additional six days.No matter -- I'm now a published app developer!
There were a couple of nagging details to tie up prior to my official app submission, however. First, I had to create a distribution provisioning profile for code-signing my Version 1.0 app. I just had to follow a few steps inside the iPhone Program Portal, then install the profile in my dev system's Keychain, and I was ready to get my app officially blessed for release in the iTunes App Store.

This graphics are easy enough: an icon (57x57-pixel PNG format image), an iTunes artwork rendering (just a 512x512-pixel JPEG version of your icon), and a sample screen grab (pick a great screen shot of your app in "motion"; this image will go on your "storefront" iTunes page. So, think "eye candy" here -- sell that steak app with a juicy, sizzling screenshot.
Use this form for handling those last-minute application information queries:
App Store Application Information
You should also keep an eye on your app size. There is a 10MB limit on over-the-air "sales" of apps. Luckily, my behemoth app, tipping the scales at 7.7MB, was able to just skim under the limit. This heft is from all of the CAF audio files (156 different audio files) embedded inside the app.
There are some additional questions regarding games, encryption, and licensing agreements. If your app doesn't fiddle around with these items, then you're home free and ready to complete the submission process under the purview of Apple's overtaxed review board.

Another problem looms on the horizon, however. First-time Apple developer's contracts are being processed at an increasingly slowing rate. Likewise, current developers who wish to renew their license might be in for a wait, too.
No matter -- I'm now a published app developer!

Finally, by the numbers: RingsTrue (my musical name game app), upon its initial release, logged 37 downloads. Housed in the Music category of the iTunes App Store, RingsTrue failed to receive any promotion, mention, or placement on the iTunes daily "New" display. Therefore, these "sales" were obtained solely by random browsing of the 30,000+ iTunes App Store apps. I will update these download numbers as significant milestones are reached.
Update, March 25, 2009: Downloads for RingsTrue just broke the 100 mark.
Stay up to date on the latest news of the future of science and technology from your iPhone with full articles, images and offline viewing
Featuring every article from the magazine and website, plus links from around the Web. Also see our PopSci DIY feed
Share links with friends, comment on stories and more
In our December issue, Popular Science names the 100 best innovations of the year: bombproof wallpaper, self-parking cars, the fastest helicopter, and 97 more. Plus inventor profiles and videos.
Check out the best of what's new here.




You're right. Getting the app blessed is the hardest part. My keychain and Xcode had the app info, but when I upload it to iTunes, it says that it is not code signed. I'd like to see a few more steps or screen shots on the process of code-signing. Thanks.