Well, thanks for the info. I was prepared it all works like that :) And I came up with the following: (1) We obligate user to run application within N minutes after the purchase. (2) Every N minutes we update application on the market (each update effectively updates an unique id inside of application). (3) On the first run we activate an app (sending phone id to the server; server can deny activation). (4) And finally, we accept activations of the given app id only within N minutes.
This effectively restricts lifetime of pirate copy to the N minutes. The downside is that we screwing up the whole update system of the market. The upside of that, in turn, is that maybe google will finally pay attention to the problem :) Dmitry On 24 ноя, 16:28, String <sterl...@addressender.com> wrote: > On Nov 24, 10:15 am, "Dmitry.Skiba" <dmitry.sk...@gmail.com> wrote: > > > (1) Be able to supply an unique token to the user when he buys an app, > > and have him enter that token later in the app to activate it. > > Short of (a) requiring the user to send you personal information, and > (b) manually matching up that information with the cleared > transactions on your Checkout account, I don't think this one's > possible either. The problem is that there is no automatable way to > distinguish a paid Market user from a pirate, and thus no way of > knowing who you should supply said unique token to. > > The bottom line is, Google is the only one who can fix the Market's > security. The rest of us just don't have the required tools. > > String -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
