As there seems to be some confusion by some people on what constitutes a Beta, here are three excellent definitions. Tell me you don’t understand a Beta without telling me you don’t understand a Beta.
Of course, Wyze can go it’s own way, but the earlier goofballs who called me arrogant clearly have no substantiative experience or knowledge. I’ve worked in multiple software products, all of which followed the basic principles below. We ALWAYS involved the users - it’s almost a basic requirement of a Beta to validate our users will see a GA product that meets their needs.
So who’s being arrogant? A Wyze VP had obviously gotten wind of user complaints, and maybe the comments about legality. He found time to update us, even though he gave very little. But he gave an expected GA date! So this thing will be in “Beta” for a year. No working with users, no updates, and no confidence.
The real question, is why would Wyze not follow these perfectly good guidelines? I’m sure there are many reasons, not least being costs, staffing, and workload. But come clean and be honest about some of the concerns! “We are working on it, but it’s currently best-effort due to conflicting needs”. That’s basically what the VP said - we’re working on Firefox (how long does it take to fix that? It should not be months). So stop calling it a Beta and call it a preview - no user input wanted thank you. At least be honest with us.
“In software development, a beta test is the second phase of software testing in which a sampling of the intended audience tries the product out . Originally, the term alpha test meant the first phase of testing in a software development process.”
“Software developers release beta versions of software in order to garner useful feedback before releasing the final version of a program. They often provide web forums that allow beta testers to post their feedback and discuss their experience using the software. Some beta software programs even have a built-in feedback feature that allows users to submit feature requests or bugs. In most cases, a software developer will release multiple “beta” versions of a program. during the beta phase. Each version includes updates and bug fixes that have been made in response to user feedback. The beta phase may last anywhere from a few weeks for a small program to several months for a large program.”.
" Beta, is the software development phase following alpha. Software in the beta stage is also known as betaware . A beta phase generally begins when the software is feature complete but likely to contain a number of known or unknown bugs. Software in the beta phase will generally have many more bugs in it than completed software and speed or performance issues, and may still cause crashes or data loss. The focus of beta testing is reducing impacts to users, often incorporating usability testing. The process of delivering a beta version to the users is called beta release and is typically the first time that the software is available outside of the organization that developed it. Software beta releases can be either public or private, depending on whether they are openly available or only available to a limited audience. Beta version software is often useful for demonstrations and previews within an organization and to prospective customers."
I don’t really see why I should have to point how to run a Beta, or how to run a company that respects it’s users (no, let’s make a gun safe instead!). Revenue is vital for the long term of the company, but if you lose customers due to an unwillingness to communicate, then you will customers and revenue.
Wyze was started by Amazon employees? I’ve never had a single bad customer experience with Amazon - their support, for such a huge company, is extremely good. It’s a shame that customer focus never made it to Wyze. Since you still work with Amazon, why not ask what you are doing wrong, and why you insist on being insular and unhelpful? Maybe they could give you some tips, since my comments are clearly not welcomed.