Friday, November 30, 2012

[android-developers] Best approach for incorporating in-app purchase demo code into real project.

The 'Dungeons' demo code goes to some length to emphasize the security issues involved in implementing in-app purchases.  One thing it makes some issue of is being careful about dropping the demo code into an existing project as opposed to reimplementing it from scratch (ugh).  I'm using CodeDefender (or whatever it's called, I don't have it in front of me right now) for basic obfuscation, and I certainly intend to "mix up" the demo code some...but I'm curious if there is a more explicit prescription for how to fold in-app purchases into a project.  Would others strongly advise against literally duplicating the Dungeons code into a subpackage of my actual project and then proceeding to make various cosmetic, yet functionally null, changes to the code?  Is there a better way to accomplish this overall task?

Thanks.

--
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+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

0 Comments:

Post a Comment

Subscribe to Post Comments [Atom]

<< Home


Real Estate