Because "We are using Java and hence risk of code stealing would always be there for us." Does not seem to have anything to do with reverse engineering authentication policies.
Hope this helps, kris On Dec 7, 2011 3:36 AM, "Anil Jagtap" <[email protected]> wrote: > > I wonder what made you think I did not understood what 'he' means. I > know perfectly and that was the answer! > > Cheers > > On Dec 6, 8:41 pm, Kristopher Micinski <[email protected]> wrote: > > On Tue, Dec 6, 2011 at 8:37 PM, Anil Jagtap <[email protected]> wrote: > > > Even if the application is reverse engineered and say an cracker gets > > > 100% of your code. Still, what is use? it is your app that is first in > > > android market in case of android market apps. If someone makes a > > > clone, it is still a 'clone' and you are the original. We are using > > > Java and hence risk of code stealing would always be there for us. May > > > developing in C may help, but again it has its own complications. > > > > > Cheers > > > > That's not what he's worried about, > > > > he's worried that somebody will reverse engineer some authentication policy > > or something and reveal something other than just the source to the app.. > > > > kris > > -- > 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 -- 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
