2 ms·
If its already in beta then why do you want to limit the # of people who are actually excited to try out your application? If its not ready for prime time then
by vaksel 18y ago
If its already in beta then why do you want to limit the # of people who are actually excited to try out your application? If its not ready for prime time then call it an alpha.
To me Beta is pretty much something that's ready to go prime time, everything works, you spent a few days testing it to make sure you don't crash the system, but you still want to spend some time with a much larger audience testing it to sort out all the missed bugs. Alpha to me is when you just finished coding it up and only did the most basic stuff to check if everything works.
If its an alpha then use the one at a time invite, if its beta set max # of users and use one at a time method if you need to give out some extra invites to more valuable testers
- Zev 18y agoOne problem with what you're saying is how you define "beta". Everyone defines it differently (What Google considers beta is different than what I would consider beta which is different than what you consider beta. A larger problem (you're not alone in making this mistake) is trying to lump software development into set, solid stages. Development is more fluid then "OK. we're beta. next up is final release and we're done forever." It's doubtful that you ever stop adding features or making something better. And if that is the case, I'm not entirely sure I'd want to use your product knowing it'll never be improved beyond 1.0. As for why you might want to limit invites? Maybe you're trying to figure out how much it can scale with what you currently have before you work on it some more? Or maybe you want to try the limited scarcity thing out. Who knows the motivations.