Another major fail by a company that is "distributed" and does not fully understand technology is actually harder and more time consuming than they realized. Add to this the group added networking to a traditionally non networked product, took a 3rd party interface spec at face value, did not fully vet the product and did not know that wireless networking is full of WAY more minefields than wired networking.
Then we end up with a classic case of "Over Promise, Under Deliver".
Uniden had too many cooks in the kitchen, firmware developer(s) outside of the US that are non native English speakers, this just means DELAY after DELAY with differences in cultures, Time Zones, Holidays, different management priorities and on and on. In my experience, there is usually a "Firmware Developer" ie singular not plural. So if you loose the 1 guy, you are screwed.
Then Uniden was sitting back waiting on the wireless dongle vendor to resolve things. Again, many of the problems above probably factor into what is going on with the 3rd party dongle vendor - firmware developer(s) outside of the US that are non native English speakers, this just means DELAY after DELAY with differences in cultures, Time Zones, Holidays, different management priorities and on and on. In my experience, there is usually a "Firmware Delevoper" ie singular not plural. So if you loose the 1 guy, you are screwed. Then add to this ALL the wireless standards and minor issues that have to be tested, fine tuned and vetted. Wireless stuff is a PITA to get fully sorted out and tested.
Then add to this the App developer(s). Not sure if they have a single person or group for the Apple and Android Apps or a person/group for the Apple App and a person/group for the Android App. What happened here is nothing major, if anything was accomplished with the Apps because the WiFi dongle was not working. So the old chicken and egg problem. How can the App guys move forward of the networking of the unit is not resolved??
Then add to this the entire centralized server aspect for the Siren App. Uniden or a sub contractor has been probably procuring hardware, configuring it, moving it around, changing/updating ISP connections and possibly even procuring/changing hosting companies, web and IP addressed.
So this probably will take a small army of people that were never planned for, budgeted for, hired/sub contracted for. There was probably details specs/statements of work ever developed as this was probably all back of the napkin/white board stuff buy people that had NO idea of the level of difficultly, time and labor requirements. How do you convey to a person what is needed with a few sentences? If there are no firm requirements, then you leave the design up to the firmware developer that may or may not know what is really needed to get the system/product to work.
Add to this the need to get the Analzye Feature released, basic decoding and feature updates and tweaks, what is the priority, who's on first, who's responsible, where are the people, how long with this take, who's budget will all of this come from and there are WAY too many unanswered questions!!
Yes, I have read this book, seen this movie, been on the edge or had to support some of these endeavors, so I know all well how easy it is for some Non Technical Manager to say this is what we are going to do and lets get this done by the end of the month!! Little do these Non Technical Managers have an idea of the scope of some of these seemingly simple things they want to deliver can bankrupt the company in many hours of development and endless delays.
As this all starts to spiral out of control, the firmware developer get crapped on time and time again, given unrealistic deadlines and are worked like dogs. I have seen the very unfortunate situation where the firmware developer just throws their hands up and the air and almost goes postal, many times walking off the job and often away from the company for good. If Management does not "Manage" the firmware developer(s) tasks, workload and priorities and "insulate" the developer(s) from the chaos thing can go bad very quickly.
I hope I am totally wrong on all of this, but I have seen this over and over with many different companies doing very unique and cutting edge things and it is sad to see things that should work, be delayed and fall apart after a lot of effort has been expended.
Technology is neither quick or simple these days, especially when you have cross discipline folks involved with product development.
I stay optimistic we will see some progress this year, but being in the trenches I know how slow and difficult these tasks can be.
Good luck to everyone on both sides of the product. I hope money and time does not run out.