Test , test and test some more if you think the app is ready for the app store !!!! delete the test app off your device !!!!! quit Xcode and clean out ~/Library/Developer/Xcode/DerivedData manually. Remove all its contents because there's a bug where Xcode will run an old version of your project that's in there somewhere. and test some more if you happy submit away. seeing too much buzztouch apps that don't that the complete app causes end users have to do too much refresh.

Excellent advice! There's no such thing as too much testing (well, maybe "tooo" much testing), and I love the idea about cleaning out that folder. Each person should strive to have the absolute best user experience for their customers the moment the open the app for the first time. I also advise to NOT touch your app at all in the control panel after you have submitted it and until after it's been approved. Otherwise, you guarantee that the reviewer will get the "This apps content has changed..." message, which is not a good first impression. Finally, give strong consideration to an offline vs. online app, and how that affects your ability to do updates in the future. There are serious implications with both ways! Mark

with my APKs for droid, i typically "pass out a taste" among my buddies and have them rip it apart. I just send them the APK by email and they send me all the ways it is screwed up. If you have a couple of mates with jailbroken phones, you might can do the same thing...your own little beta testing group