Due to the nature of web and the increasing security risks, if you want a desktop application to respond to a web page click, the most common way today is to use a custom protocol to pass the data.
Now, use GitHub Desktop as example. Upon installation, this desktop app registers itself in Windows so that it can handle requests like x-github-client://something
, and then when inside a web page this kind of links are clicked by the users, they might be opened by GitHub Desktop from the same machine.
Back to your scenario, you really need to know what kind of desktop software you want to integrate with. If the software has a similar custom protocol similar to x-github-client://
then you just need to embed the proper links in your web application to enable the integration.
If the software does not have such a modern feature, then you might develop your own desktop app with such a feature and suggest your customers to install it alongside the original software. So, your web application uses the protocol to launch your own desktop app, and in turn your desktop app can kick out the original software (since both of them are on the same machine, your app can integrate tighter via all possible ways).
Don't use ActiveX now, as modern browsers dislike that legacy approach.