Return to Answer

Do not distribute standalone software to people. I repeat: do not distribute standalone software to people. Unless it is absolutely necessary or it is the nature of the software (e.g. video games).

Maintenance is a nightmare. Versioning has so many consequences. First, you need to distribute each new version. Which already is painful. But what is worse, it is likely you have to support old versions. At least up until some point. Because you can't force people to actually use newer software. Unless you want to experience their fury.

So just keep everything in your web app. If you want, you can give your users a separate software. But what I suggest is: software as a service. You can setup a validation service for their data, why not? You still have similar versioning issues, but at least you have full control now, and can actually enforce stuff on people if needed.

Trust me, it is a lot easier if everything is under your control. People are just... Eh...

The only reason to actually distribute such software is if the data is huge, say in GB or at least hundreds of MB. Otherwise, don't bother.

Also it would be beneficial to keep such package in entirely separate, independent repository. It is easier to track changes that way. And since you have to setup some build and publish process anyway, then there's no benefit of keeping it together with other code.

Do not distribute standalone software to people. I repeat: do not distribute standalone software to people. Unless it is absolutely necessary or it is the nature of the software (e.g. video games).

Maintenance is a nightmare. Versioning has so many consequences. First, you need to distribute each new version. Which already is painful. But what is worse, it is likely you have to support old versions. At least up until some point. Because you can't force people to actually use newer software. Unless you want to experience their fury.

So just keep everything in your web app. If you want, you can give your users a separate software. But what I suggest is: software as a service. You can setup a validation service for their data, why not? You still have similar versioning issues, but at least you have full control now, and can actually enforce stuff on people if needed.

Trust me, it is a lot easier if everything is under your control. People are just... Eh...

The only reason to actually distribute such software is if the data is huge, say in GB or at least hundreds of MB. Otherwise, don't bother.

But if you decide otherwise, then it would be beneficial to keep such package in entirely separate, independent repository. It is easier to track changes that way. And since you have to setup some build and publish process anyway, then there's no benefit of keeping it together with other code.

Do not distribute standalone software to people. I repeat: do not distribute standalone software to people. Unless it is absolutely necessary or it is the nature of the software (e.g. video games).

Maintenance is a nightmare. Versioning has some many consequences. First, you need to distribute each new version. Which already is painful. But what is worse, it is likely you have to support old versions. At least up until some point. Because you can't force people to actually use newer software. Unless you want to experience their fury.

So just keep everything in your web app. If you want, you can give your users a separate software. But what I suggest: software as a service. You can setup a validation service for their data, why not?

Trust me, it is a lot easier if everything is under your control. People are just... Eh...

The only reason to actually distribute such software is if the data is huge, say in GB or at least hundreds of MB. Otherwise, don't bother.

Do not distribute standalone software to people. I repeat: do not distribute standalone software to people. Unless it is absolutely necessary or it is the nature of the software (e.g. video games).

Maintenance is a nightmare. Versioning has so many consequences. First, you need to distribute each new version. Which already is painful. But what is worse, it is likely you have to support old versions. At least up until some point. Because you can't force people to actually use newer software. Unless you want to experience their fury.

So just keep everything in your web app. If you want, you can give your users a separate software. But what I suggest is: software as a service. You can setup a validation service for their data, why not? You still have similar versioning issues, but at least you have full control now, and can actually enforce stuff on people if needed.

Trust me, it is a lot easier if everything is under your control. People are just... Eh...

The only reason to actually distribute such software is if the data is huge, say in GB or at least hundreds of MB. Otherwise, don't bother.

Also it would be beneficial to keep such package in entirely separate, independent repository. It is easier to track changes that way. And since you have to setup some build and publish process anyway, then there's no benefit of keeping it together with other code.

Do not distribute standalone software to people. I repeat: do not distribute standalone software to people. Unless it is absolutely necessary or it is the nature of the software (e.g. video games).

Maintenance is a nightmare. Versioning has some many consequences. First, you need to distribute each new version. Which already is painful. But what is worse, it is likely you have to support old versions. At least up until some point. Because you can't force people to actually use newer software. Unless you want to experience their fury.

So just keep everything in your web app. If you want, you can give your users a separate software. But what I suggest: software as a service. You can setup a validation service for their data, why not?

Trust me, it is a lot easier if everything is under your control. People are just... Eh...

The only reason to actually distribute such software is if the data is huge, say in GB. Otherwise, don't bother.

Do not distribute standalone software to people. I repeat: do not distribute standalone software to people. Unless it is absolutely necessary or it is the nature of the software (e.g. video games).

Maintenance is a nightmare. Versioning has some many consequences. First, you need to distribute each new version. Which already is painful. But what is worse, it is likely you have to support old versions. At least up until some point. Because you can't force people to actually use newer software. Unless you want to experience their fury.

So just keep everything in your web app. If you want, you can give your users a separate software. But what I suggest: software as a service. You can setup a validation service for their data, why not?

Trust me, it is a lot easier if everything is under your control. People are just... Eh...

The only reason to actually distribute such software is if the data is huge, say in GB or at least hundreds of MB. Otherwise, don't bother.