Have you read the FAQ here? 

https://support.sonos.com/en-us/services/qobuz
 

As far as the Qobuz software, Sonos wouldn’t have access to the code base, so it really isn’t up to Sonos to ‘support’ it, it would be up to Qobuz to implement the already written API, and fold it into their own software. 

Qobuz has encouraged Sonos users to contact Sonos to advocate for Qobuz Connect integration. They explicitly suggested that Sonos users reach out to Sonos to push for collaboration on developing Qobuz Connect for Sonos devices.

Great. Unfortunately, this is a Sonos public community, and not a connection to directly pass on your comments to Sonos directly. You need to call Sonos Support directly.

And frankly, Sonos has already written the API, and provides that to anyone who wants to use it. What Sonos doesn’t have is access to Qobuz’s code base to do the integration. I suspect your contact at Qobuz doesn’t quite understand how this works. 

Connect is a built in solution. Other manufacturers have published firmware update. Sonos did it for Spotify Connect.

The qobuz app is only a remote controller. You can switch off your phone and keep listening Qobuz.

Qobuz created an SDK. It is up to Sonos to add it to the firmware of its products. Taking in account that we can’t Chromecast to Sonos, and that DLNA is not working that well, I would say that this would be a no-brainer, if technically possible on the devices.

Much smaller manufactures could do it. Sonos for sure also has the resources to do it and for sure there is a lot of overlapping between Qobuz and Sonos userbase.

You may want to read the Sonos partners page. You’ll find that Sonos doesn’t integrate other people’s SDK/APKs. That’s the entire point of Sonos, they’re an open platform, who doesn’t need to maintain a thousand coders to update other people’s code changes.