Hi BorisM,
They only need to write a new UI and package it, underneath not much will have changed audio wise, as I pointed out the app technically works on a very old OS ( audio wise ). So when Rose claims, it’s technically difficult and their testing showed it wasn’t running flawless… what exactly are they talking about ? Hifi Rose’s mothership is used to designing UI’s, don’t they ? So that is my point. They don’t want to, but claim it’s difficult, audio experience would be bad… bla bla
Regarding vulnerabilities, embedded or not, even enterprise OT environments have embedded software too, and do suffer from a lot of modern day vulnerabilities once connected to a network. ( Hence why everyone is segmentating/separating it from the rest of the network, beacause they are vulnerable and they are the most critical devices for production environment ( CNC machines as an example ). The moment a streamer uses libraries like openssh, glibc, running webservers, support Samba etc etc… they enter the world of modern day vulnerabilities ( like f.e. cross site scripting, authentication flaws, protocol vulnerabilities ). I don’t know all the details from what Rose is doing custom for Android on the streamers, but I’ve seen a lot of corporate environments, and vulnerability scans results, and you would be surprised. The time of designing a box, connect it to the network, and never update it ever again are over. Hence the measure EU took with the CRA, but I’m sure the US will have something similar or will have it in the near future. Not everyone is running the Roze streamer in a separate IOT VLAN and protects it with proper in and outbound L4 rules ( not to mention higher OSI layers, meaning more intelligent application protections, those advanced protection are mostly for enterprise with proper firewalls ). Before you know it, your streamer is running malware in a bot network. And if you think I’m exaggerating, Google for Botnets on IOT devices, IP camera’s, NAS devices, Dlink routers etc…