To beta or not to beta.. that is the question [closed]

Question

I'm looking for a consensus for one or the other

• Beta; Release software that is semi- functional to a limited audience and let users guide the process until an application is complete.

• No Beta; Define all functionality based on previous user-feedback and/or business logic, build the software, and test it with whatever time you give yourself (or are given).

Answer 1

Hmmm...Beta is for a product you think is finished...until you give the Beta users to play with it and they break it in ways you haven't thought of.
So, yes, go with Beta, unless you want to burn your product on many users.