Hacker News new | past | comments | ask | show | jobs | submit login

He glosses over beta, but that's a crucial stage for non-developers to understand. Testing your application with real, live users is hugely important. If you don't beat the hell out of it, the public will, and you don't want to end up waiting around for Apple to approve a fix for a glaring bug that pisses people off.

(Sidenote: This is the pain of experience. I once pulled one of my apps just as it got popular because of a data destroying bug that my sloppy QA process didn't catch. Just one line of code, part of final performance optimization. Harmless, right?)

I wrote up a lengthy post on doing iPhone betas last year. Maybe it'll be useful to others here, dev or not:

http://blog.danilocampos.com/2009/12/03/how-to-run-a-great-i...

And for the love of god, do one last round of exhaustive QA even after making "minor" performance improvements. :)




Actually, I specifically bring up beta testing and testing with real world customers/conditions instead of addressing Andrew's question about what's involved in submitting an app. It was that important for me to mention it. Of course, we could spend an entire interview discussing that aspect, so perhaps that is why you perceived me glossing over it. :)




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: