Have you considered adding support for running a service in the background, possibly as the system/root user? Maybe I'm working on one of the very few categories of desktop app that still need that (remote desktop a la TeamViewer). This requirement is one reason I didn't go with MSIX on Windows; MSIX didn't add support for background services until Windows 10 version 20H1 and the corresponding Windows Server version, and I don't know how long it will be until we can drop support for Windows Server 2016.
Registering background tasks, yes, that sounds general enough to include albeit we haven't yet encountered a customer who needs that so there are higher priorities.
Supporting old versions of Windows Server - probably not unless the customer signed a development contract to do that work specifically.
Our goal is to open up desktop development to people who previously wouldn't have considered it. For example if you have a mobile app and are considering bringing it to the desktop, today you'd probably have to write a totally separate version of your UI as a web app. That's sort of duplication is very expensive. If desktop development is easy then you can use Jetpack Compose, KMM, Flutter, etc to lightly adapt your mobile code and develop far faster. Another example: you can write apps that connect directly to their backends e.g. an RDBMS, without needing complex/expensive server side load balancing and the whole REST/JSON/SQL glue layer.
That's why we've really focused on ease of use and cross-platform support. You write a tiny config file that points at your build artifacts, run `conveyor make copied-site` and you're done: a release has gone out for every supported platform and your clients will start to update.
But if you have a Windows-specific app and a solution that works for you already, then I'm not sure Conveyor has much to add.
