In any case, if the exe program is needed to run your application just tell people that they need to download and install it if they are going to use your system. They can choose to follow the instructions or not as they please.
When the local program starts, it would ask the user to log in and contact the DB and write a record that records that the user has installed and run the software.
you should expect a large number of people to refuse to install local programs.
Ulf Dittmer wrote:
When the local program starts, it would ask the user to log in and contact the DB and write a record that records that the user has installed and run the software.
That would only work for the machine the user used that time, though
you should expect a large number of people to refuse to install local programs.
Given that a client relationship was mentioned I suspect that may not be the case.
Bear Bibeault wrote:If it were me designing this, I'd likely do something like the following:
When the local program starts, it would ask the user to log in and contact the DB and write a record that records that the user has installed and run the software. This would be a one-time action when the program starts for the 1st time. When a user logs into the web app, it would check to see of the record exists. If so, proceed as normal. If not, it would direct them to an instructional page where they could download the program and read the privacy policy and other policies regarding the program.
Ulf Dittmer wrote:I think we're getting lost in details, and I'm not clear how those are related to the issue at hand. Can we take a step back, and you start by telling us what the connection between that app and your web app is. Why shouldn't the user use the web app if he hasn't installed the native app? What does the client's MAC address have to do with it?
Good night. Drive safely. Here's a tiny ad for the road:
Gift giving made easy with the permaculture playing cards
https://coderanch.com/t/777758/Gift-giving-easy-permaculture-playing
|