Yep, to follow up on the previous two posts...
It seems to us (after some experimentation on the server side of things) that you really have two choices--both bad--and end up with one very vicious end when it comes to audio server stuff:
Choice 1: Hide the fact that it's a Linux computer as much as possible. Super-simple UI, no interface for updates, use physical buttons, etc. While this addresses the audience that doesn't want to deal with drivers/updates/computer crap in general, it is also profoundly limiting. What happens when you find a bug and can't do a network update? What happens when you need a new output interface, or if formats change? In all cases, you're kinda boned. But, if you do it right (big if--there is still a LOT of software work on this), you could have a magic box that, for a few years, would be relatively easy to use.
Choice 2: Embrace that it's a computer as much as possible. Touchscreen, remote via smartphone or tablet, OTA updates, etc. While this is all cool and IoT and all, you're now deep in software hell. Hell, you are a software/smart device company at this point in time. Staff up. You'll need it. This device will cause endless confusion in a large percentage of your audience. Hint: we polled a selection of our customers as to whether they'd want a remote via a cellphone app or a physical remote. Almost NOBODY wanted the cellphone app--and this is amongst the youngest audience in the business.
The vicious end: in 2 years, when the touchscreen you chose is (a) laughably low-resolution and (b) not purchasable anymore, and the software you've developed is not supported by the developers anymore (because they left for greener pastures, or code has moved on), and you have to make and support more products...well, then the fun really begins, doesn't it.
So, that's why we make Choice 3: realizing that your audio server is nothing more than a computer. Just buy a Mac, set up a Linux system, or use a Windows box. Done.