11–20 of 28 posts
You don't. Alpha tests are, by definition, internal-only.
There are several different definitions. One definition I like is that alpha testing is when you know there are still missing features, while beta testing is when the planned features exist and you're just trying to make sure that they all work properly -- in which case you could very easily have public alpha testing.
How about starting by getting some target users using it and seeing whether they spread the word and recommend it to their friends? The rest is all very nice, but a bit OTT for an alpha launch. Not putting down your work at all, but anything that hasn't got real users yet is probably still a long way from being worthy of being officially "launched". If you media-blitz and overhype it and it's not ready, you'll end up…
I have had it testing from some eBay sellers already, but certainly having it testing from couple of hundred users will help a lot.
I'd do the early phases like this: 1.) Release to family members, trusted friends & people that have a stake in the project. Get their feedback. 2.) Release on news.YC. Get their feedback. 3.) Find some influential bloggers in your field. Don't release to them; instead, send them a personal e-mail asking for their feedback. 4.) Go to forums in your field, pick out some dedicated early users that are really into the s…
Any idea on how to find influential bloggers? (Besides Googling) Like is there any blog searching place that shows me ranks of blogs (based on traffic) and and have those distributed in categories like (Technology, Business, E-commerce, blah...)
You don't. Alpha tests are, by definition, internal-only.
Alpha tests are, by definition, internal-only. There are several different definitions. One definition I like is that alpha testing is when you know there are still missing features, while beta testing is when the planned features exist and you're just trying to make sure that they all work properly -- in which case you could very easily have public alpha testing.
Hey, I Googled 'Onista' and found your recent Vimeo video: http://www.vimeo.com/1376104 as well as some introductions in various forums. Looks like you're building up the hype well. My 2c after watching the video: I don't understand the instant negotiation. Is there a limit on the number of times I can submit a bid? If not, can't I just start really low and then increment by $1 or $2 until I meet the minimum? If ther…
On Onista, users can pay each other the same way they do on eBay.
Paypal, Credit Card, Money Order, Cashier's Check, Personal Check
I'd do the early phases like this: 1.) Release to family members, trusted friends & people that have a stake in the project. Get their feedback. 2.) Release on news.YC. Get their feedback. 3.) Find some influential bloggers in your field. Don't release to them; instead, send them a personal e-mail asking for their feedback. 4.) Go to forums in your field, pick out some dedicated early users that are really into the s…
Sounds like a good plan and yes this is what we shall do. Iterating is the best approach as we get some time to fix the issues before more users know about it. Any idea on how to find influential bloggers? (Besides Googling) Like is there any blog searching place that shows me ranks of blogs (based on traffic) and and have those distributed in categories like (Technology, Business, E-commerce, blah...)
Earlier quoted context omitted.
Alpha tests are, by definition, internal-only. There are several different definitions. One definition I like is that alpha testing is when you know there are still missing features, while beta testing is when the planned features exist and you're just trying to make sure that they all work properly -- in which case you could very easily have public alpha testing.
We have done lot of testing on our application using some external users as well and fixed close to 2k bugs to make it more stable. As you are suggesting, we are planning public Alpha.
If you do announce something, don't call it a 'launch' call it an 'alpha.' When you do a beta, call it a beta. Don't use the word launch until you're ready, b/c any news is going to say "But you launched in August! What's new?" and all you can say is "We're out of beta" or something like that.
Thank you very much.
Earlier quoted context omitted.
We have done lot of testing on our application using some external users as well and fixed close to 2k bugs to make it more stable. As you are suggesting, we are planning public Alpha.
The definition I like is that you must fix at least 3k bugs before a public Alpha. Looks like you're 1k short, buddy.
To find those more 1k bugs to fix I would need to open it to some users. We are testing it almost everyday and now are unable to uncover more bugs. I mean bugs will always be there. Windows XP has lot of bugs. As I am advised by others, at one point if you feel codes is stable enough, you need to open it to get more feedback.