I know this is a bit old, but last time I posed the question, the UDI folks said it takes a lot to rebuild that UI (which I can agree with, testing being a huge bear) and that it's just not as high a priority as other things in the queue (risk/reward-wise, and they have a LOT in the queue compared to developer time).
We can all agree that at some point they'll need to bite the bullet and do it. And they'll need to do it before some competitor(s) erode their position beyond recovery. I don't say that as posturing - I love my ISY - but it's just a reality and having zero knowledge of their internal priorities, finances, etc, I can make blind statements like "it worries me when this doesn't get more attention." UX is a pretty critical selling point these days. Having your product's usability saved by the virtualization afforded by your customer's surplus processing power isn't a good thing. Managing containers/VMs is yet another barrier to entry for casual adopters. I loathe having to install crapware on my machine, and as a former enterprise IT developer and manager, JRE has been in that category for well over ten years (not trying to offend anyone, it is what it is).
It seems to me that this would be ripe for open-sourcing. I don't know how much the software accounts for UDI's IP and value vs the hardware device, but I really wonder if they've seriously considered this option. Developer resources are scarce, I get it. But open source it - even if your code is dirty and embarrassing - let the community submit candidate updates, do testing, etc., and UDI can still control what's "official". They'll probably still be the main contributor, but if the community can help them get an alternative interface kicked up, that's gotta be a great thing.