A way to generate watermarked test packages

Welcome Guest! To enable all features please Login or Register.

Notification

Error

A way to generate watermarked test packages

Options

Previous Topic Next Topic

saviilsy		#1 Posted : Friday, March 23, 2012 1:31:54 PM(UTC)
Joined: 8/24/2011(UTC) Posts: 95 Thanks: 6 times Was thanked: 2 time(s) in 2 post(s)		Hi! One cool feature would be to generate multiple installation packages that would be watermarked somehow. A scenario : You start beta testing Your app, and generate installation package for all Your 200 facebook friends to try it out. One guy decides to leak the app to the world -> no way to find out who(happened to my friend). If we could generate a unique id for every test package, we could identify the source of leakage for example. Of course One should be able to read the watermark back from the installation package somehow. Just an idea...


User Profile View All Posts by User View Thanks


	Wanna join the discussion?! Login to your forum account register a new account. Or Connect via Facebook Twitter Google

elasto		#2 Posted : Friday, March 23, 2012 2:02:33 PM(UTC)
Joined: 8/23/2011(UTC) Posts: 245 Thanks: 6 times Was thanked: 12 time(s) in 11 post(s)		I've thought about this kind of thing. The problem is that what are you really going to do with the knowledge of who it was? They'll probably just tell you they let a trusted roommate/friend/family member try it out and it was them that must have passed it on. What are you going to do, sue them? Unlikely. It would probably be more useful just to time or feature-limit installation packages you hand out for Beta testing etc. I've never released an Apple app but I assume there's a way to invite a person to receive a free Beta key - and they can no more share the app than a person that paid for the app could. The other factor is that, ideally, you want people to be passing your app on. You want people to be enjoying it so much they pass it on to their friends and the buzz begin to build. That's why a lot of games follow the free-to-play model these days - either then relying on adverts or on selling in-game add-ons or both. Personally when I pass out Beta versions of software I will be doing it assuming - hoping even - that people will be passing it on to friends. And in any case I'll also be assuming that the app will eventually get cracked. If noone bothers to crack it then it's probably not that good/popular an app and I'm out of luck anyway! (It'll be a weird badge of honour when I see my first app/game showing up on the P2P networks :p )


User Profile View All Posts by User View Thanks

Benjamin		#3 Posted : Friday, March 23, 2012 2:35:07 PM(UTC)
Medals: Joined: 8/20/2011(UTC) Posts: 1,421 Location: Hannover Thanks: 18 times Was thanked: 97 time(s) in 92 post(s)		Originally Posted by: Santtu Syrjä Hi! One cool feature would be to generate multiple installation packages that would be watermarked somehow. A scenario : You start beta testing Your app, and generate installation package for all Your 200 facebook friends to try it out. One guy decides to leak the app to the world -> no way to find out who(happened to my friend). If we could generate a unique id for every test package, we could identify the source of leakage for example. Of course One should be able to read the watermark back from the installation package somehow. Just an idea... You could set a custom installer script (via Framework Key) when building your application with the Launcher (or just change the version number). Then you could track which version you send to which person, but this is in no way automated yet and would be a lot of work if you want to build 200 versions ^^ To limit preview releases apps usually check the date, connect to the internet to allow starting, limit the ip addresses or check for specific usernames. Obviously all of these can be hacked, but it is a little harder then to just copy it away. BTW: The same problem applies to other pre-release software and even movies. In the end there is not much you can do after the file has been shared or even cracked (and you probably will never find out who did that for your application anyway). Other than that I second PGs response. If you really want a Beta-Test and keep it closed, then implement some form of protection (e.g. check via Internet), but don't be surprised if someone hacks it ^^ Usually it is the other way around, you should be happy if people share your application and if you get free marketing this way. Obviously this does not help you if you want to sell your app, which is pretty much the same as your beta, but then again you have problems protecting your app anyway if it has no protection. Or just live with it like most indies do (no DRM for the win). I personally would try to go the free to play route. Edited by user Friday, March 23, 2012 2:38:07 PM(UTC) \| Reason: Not specified
		WWW BLOG

User Profile View All Posts by User View Thanks

Rss Feed

Atom Feed

Users browsing this topic
OceanSpiders 2.0

Forum Jump

You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.