Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have a project that I would like to start beta testing soon, it is a PHP/MySQL site for programmers. I have beta tested sites before however it was always in-house, and I have never done betas that could/should be seen by someone other then those associated with the project.
How should I go about starting the beta, and what problems, aside from those the beta is supposed to expose, should I be prepared for?
First, accept the fact that problems with your app (code, usability, etc.) will be discovered.
Then, make sure you have a clear way for users to communicate with you (form mail, email, uservoice, etc.). The easier you make this the better. For example, there is a uservoice link on every page of SO.
One philosophy I strongly believe in: if it’s confusing to your users, it’s broken. Be willing to change your app (no matter how ‘beautiful’ the design may be) if your users are confused or not liking it. This doesn’t mean you have to cave on your decisions, just that you need to consider revisions to improve the user experience.