Hi guys,
i will publish a closed alpha of my app but this build should only work to the moment where i say stop. Then the build should show a message that the alpha is over.
You can give me a tip for this?
Thanks a lot.
Have it ping a server every time it boots up or on the hour or so. If your server doesn’t respond, don’t open the demo.
Pretty much what @newjerseyrunner says. Just keep in mind that this is exactly the same as any other DRM / copy protection in that it’s only useful until someone cracks it. Even for people with far more experience and/or money than us that often doesn’t take long once your thing is well known.
Only way to be safe is to only include a part of the game in the alpha build. But once the game is fully released it will be pirated anyway.
But if its pirated thats a good thing. If it’s not pirated it means it haven’t made a big enough buzz 
Yup, it’s be super easy for someone who knows what they’re doing to insert a new entry in their etc/hosts file and pretend to be your server. Maybe have the game send out a password that has to be responded with another password.
Ok thanks. I found remoteConfig and with that i change isAlphaAcitive to false. Than the startmenue is not visible.
It’s a game of cat and mouse. Two methods to work around that immediately spring to mind.
The fundamental issue is that if all of the logic and info to decide whether or not to run is on the client machine it’s all vulnerable. If your game has an online component then you can work around it to some extent, by holding back some part of the game itself on the server. Then you can perform authentication on a system you trust, and only provide access to that bit for those who pass authentication. You’d better make sure that what you’re keeping isn’t something that can be stolen or replicated, though…
No easy answers on this one.