On this track, if the idea is to make it hard for the repackagers, you can
check your package signatures to make sure they were signed with your
private key and if not, raise an error (and perhaps send yourself an email
alert). You can do this by embedding your public key in your code and use
it to verify a signature.
Now if you are worried about reverse engineering so they can steal
algorithms/ideas, {Dex,Pro}guard are the obvious options. They don't solve
everything, but a lot of things.
On Wednesday, April 15, 2015 at 9:14:58 AM UTC-5, JackN wrote:
>
> Use your mind. Generally, these APK repackagers go for the first version.
> When you deploy your app, have it shut down at a predetermined date. Make
> sure you put out an update prior to the cut-off date that either disables
> the shut-down, or furthers the date.
>
> All of the people that got you app from the repackagers, will find the app
> no longer works. You can advise them to download from official sources at
> that point.
>
>
--
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
---
You received this message because you are subscribed to the Google Groups
"Android Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to android-developers+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
