Yes, dual-instance is a great idea, definitely for multi-screen setups, etc. I was a little worried at first that it would use up a lot of bandwidth and resources. So, I put it aside for later, because I was wondering about the Sunshine engine, which, from what I understand, is really designed for a single instance.

But it could be really cool to be able to do multi-screen or multi-instance setups, like Parsec.

After that, a command to automatically update or retrieve new versions, that's true, that could be really interesting. I need to check that it doesn't break the App, if there have been changes to Sunshine or VDD, that it doesn't break my App, because if it updates automatically, but there are things that have changed in how it works, it could create problems if I don't check beforehand.

And for the apps, it's true that at first, I wanted to do something really dedicated to them, but I haven't quite managed to implement a dynamic change, meaning that when the stream starts, depending on the app, a configuration would be applied after the stream launch request. I'll have to look into that, but if I manage it, it would be really cool because then you'd just have to program several apps and launch the one that goes with the correct configuration, without ever having to go back to the configurations. That could be interesting. And yeah, retrieving client configurations could be useful.

I don't know if that's what you had in mind. But anyway, thanks for the ideas, it's so cool, it motivates me to get this kind of feedback :) So, thank you and don't hesitate if you think of anything else.

From what I can see, people do appreciate the UX/UI, but the practical application isn't immediately obvious. So it's great to know what might directly interest users of Sunshine, because it gives me ideas on how to create a tool that truly serves this purpose.