Reading the steps posted at
http://www.mobilecrunch.com/wp-content/uploads/2009/11/urbian_ringz_android_in_game.png,
I can definitely see how they might do it. The key is in screenshot 4,
"installing" the level pack. This isn't really installing, you
understand - the APK was installed in the previous step. My guess is
that (before copying the level pack from the APK) this pseudo-install
step registers the purchase with the Urbian server, and from then on
its locked to the IMEI, the original install of Ringz, or something
else tied to the individual user. I wouldn't be surprised if this step
also deletes the APK when it's done, if that's possible from within an
app (I've never looked into it).
But what if the user copies the APK before this step? This is the big
security hole in the Android market; anyone with a rooted phone can
copy out an APK, even a "copy-protected" one. I can't envision a
mechanism by which Urbian could prevent this; their application code
isn't in control until the user runs ("installs") the level pack.
String
On Nov 30, 8:47 pm, Spencer Riddering <[email protected]> wrote:
> So, I'm pretty familiar with the options available for application
> copy protection. Recently I read this article in TechCrunch
> (http://www.mobilecrunch.com/2009/11/23/ringz-first-free-android-app-w...
> ) where they claim ".. some users tried copying the Level Pack files
> to a different path on an SD card to return them later and then use
> the extension for free – but this won’t work with their app."
>
> So, I'm wondering how do they do that. Are they just enabling copy
> protection? or is there some trick that I'm not aware of.
>
> If anyone has a guess or definitive answer, I'd be interested to hear
> it.
--
You received this message because you are subscribed to the Google Groups
"Android Discuss" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/android-discuss?hl=en.
