I'll purchase their competitors product

It all depends on your locations wifi usage on the 2.4 gHz band. Only 3 channels and if they are heavily utilized or have high noise levels you are looking at problems. Sonos is making good use of the other bands but the 2.4 is still needed.

The number of visible SSIDs isn't a reliable indicator of a channel's usability. Both the usage by the SSID and the signal strength are what matters, so lots of lightly used SSIDs or low signal strength ones are rarely an issue.

As an example, my SSID is lightly used and I have my transmit power set to Auto (usually selects medium) so I have almost no impact on any but the five surrounding houses, even less on the three across the street. BUT when I decided to stream high frame-rate HD video from seven IP cameras I pretty much wiped out my channel's usability for several houses each direction. Signal strength stayed the same but channel utilization was around 70% which gave folks on that channel (including me) fits trying to use it.

Finding a reliable device or app to look at the whole wifi channel situation is complicated. The Ubiquity WiFiman App is decent.

But those who made the old (gold) app and firmware did it much finer, agree? 😁

Where have all they gone? 🤔

I don’t have any inside information, but I imagine there was a great degree of overlap between the two.  No corporation puts brand new personnel in charge of the design and implementation of a rewrite.  As to the defects in the rewritten app, by all accounts the technical team was “screaming and yelling” at the suits to not release it because they needed more time to fix the bugs.  Their concerns were ignored because capital investors were promised new hardware by end of fiscal year. 

This all is an old, well-known story.
But after 1.5 years it looks clear that there are more fundamental issues with this infamous “rewrite” than just unfixed bugs.
Seems that the Sonos network architecture change for the sake of “new, modern libraries and API’s” made the devices more vulnerable and sensitive to users’ network config variations and imperfections.
Whether mDNS itself is buggy, or just not suitable for the Sonos devices’ network interactions, or Sonos devs use it wrongly, the decision to replace the working UPNP appears a major architectural flaw.
Was this really necessary to support that “new hardware” (Bluetooth headphones 😉)? No way.

The number of problems seen has dwindled to almost none compared to what they were.  If we see one new complaint a day, it’s a big deal.  And those are usually from someone (like the OP) who is lobbing threats rather than requesting help.

Just playing “Devils Advocate”. Below are two “cherry-picked” reviews on the BlueSound Pulse speaker. The reviews by no means speak to the overall opinion/quality of BlueSound speakers or the BluOS.  However, I wonder what I would see if I were a member of the BlueSound community simliar to this one. Just food for thought….”is the grass greener on the other side of the fence”

And the number of those here who proudly have no problems is even less. 😀
Not all who have problems are writing here just to get yet again the same “it’s your network” advice.
Perhaps they are too busy rebooting and restarting their players and routers in endless cycle or hanging on their phones trying to get help from Sonos support. 😄
Instead of just enjoying the music as before 7 May, 2024.

Deciding the problem isn't the problem and doing things that don't  solve it isn't a path to a solution.

Took me far too long to realize that, and to fix the real problems here, much happier now.

People who aren’t sick don’t go to the hospital and announce “I’m proud of the fact I’m not sick today!”. 

I’ll just leave it at that. 

Oh you young folks, I start every morning by announcing "I'm not dead yet!" not taking any chances. :-)