No worries buddy. I do know that some of the founders and top leaders for Wyze are indeed American. It is my understanding that while some of them may have been born in China or elsewhere I think most of them are US citizens, or at least have lived and worked in the US for a long time. Still, there could be some cultural differences. but even within the USA, we have huge cultural polar opposites all over the place.
Still, I don’t really think culture is the main issue. I think it’s mostly business.
- How critical is something. Does the thing work okay as it is?
- What percentage of people would truly need or use it, or is it more of a niche thing?
- What will be the overall cost/benefit ratio? Is it proportional? How much effort will it take? Can we adopt open-source solutions and just do slight modifications to make it work for us, or are we going to have to rewrite everything from scratch? How much testing is it going to take? Could it cause more problems in the ecosystem in any possible way?
- People love to complain no matter a company does, but in the end, words are words and overall profits sometimes tell a different story. Ironically, we can see lots of cases where a company improves more and more, offering more and more and yet there are more complaints and criticisms in both frequency, and degree/severity. This doesn’t usually mean the company is worse, and unbiased analysis will often show the opposite, but as a company gains more success it almost always increases in opposition too.
If we compare a list of things Wyze has added and improved to a list of things they’ve removed and taken away, it is easy to view all the software and firmware update notes and see the list is easily hundreds or thousands to one.
I am with you though, it can be frustrating that some of my own favorite requests like this one have taken so long to implement while others I don’t care about at all have already been implemented. I expect part of it has to to do with the amount of effort required for that implementation as explained above. Most of the things I want the most would also be the hardest to implement and require a lot of coding from scratch and a lot of testing while other things that do get implemented are simple or had opensource code that could be copied to save time.
I could certainly be incorrect, but having coding experience myself, and having owned and operated multiple businesses, including right now, and having to make similar decisions, I am fairly confident much of it is as I described. We’ve had employees and clients/customers think things looked arbitrary when we implemented things, but things were rarely as simple as they appear to those who don’t know everything involved.
Regardless, the more people who give things like this attention, the more likely Wyze is to think it is a higher priority issue based on the above list as they consider the cost/benefit ratio. So adding to the discussion as you do is very helpful.