I'm wondering how I can effectly protect my JS logic inside the frontend from being copied by any of our competitors.
Is there any good pratice aside from uglifying?
1–8 of 8 posts
I'm wondering how I can effectly protect my JS logic inside the frontend from being copied by any of our competitors.
Is there any good pratice aside from uglifying?
You're going to have to concede some parts of your app to public scrutiny; if a JavaScript interpreter can understand it, so can savvy humans. Don't waste too much time pushing that particular stone up the hill, it will only roll down again.
Disable the console.
The only way to secure your product is to make the client depend on algorithms running on your server. That's also the reason why most popular computer games are becoming "online only" recently.
That being said, if you're willing to change up your design pattern a bit, and push more logic to the server you can get your js down two a much thinner client and handle your business-logic away from prying eyes.
But IMHO, reverse-engineering a product is very easy for the vast majority of cases, even if you can't see the code. So they're going to figure out a way to copy you regardless. There are only a handful of companies left who are doing something that others have a significantly hard-time reverse-engineering. Your codebase is valuable of course, but it's rarely a meaningful competitive-edge.