On Fri, Nov 11, 2011 at 11:45 AM, Chad Ata <[email protected]> wrote: > Thanks for the response Nikolay, > > I was hoping to avoid server-side checks because I don't want potential lag > or bugs to affect the legit users. But I'll consider your suggestion if this > becomes a big problem for us. >
You could embed the hash as a resource with a non-obvious name, and tripple-base64 encode it for extra fun if you don't want to use a server. If they are changing/modifying your resources, it might be better to store bits of it in code and calculate it dynamically though. -- You received this message because you are subscribed to the Google Groups "Android Developers" 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-developers?hl=en
