1) If you believe that someone could trawl through the code to an average app and find malicious code that had been purposely hidden there, then I have a bridge I'd like to sell you.
2) I wouldn't been keen to hand my source over to anyone. It's bad enough that the code can be roughly decompiled. William On Monday, October 1, 2012 5:24:57 PM UTC+10, Matt wrote: > > Sorry if this isn't the right place to suggest things like this, if you > could direct me to the right place then that would be appreciated :) > > > > Ok, so last night me and a friend are having an iOS vs Android debate, me > obviously backing android. The only major concern we both shared with > Android was how easily a malicious developer could get an app onto google > play and then have it downloaded by basic users not really knowing what to > look for in the authenticity of apps. > > > > We just thought maybe there should be two layers to google play apps, one > where the source of an apk is explored by an employee and confirmed to be > safe and another where the app has not been confirmed (or verified) to be > safe. Both being accessible just the latter disabled by default. After an > app has been downloaded say 1000 times it's put in a queue to be verified > and if found to be malicious is nuked. > > > > Not sure what you guys think. > > > -- You received this message because you are subscribed to the Google Groups "Android Discuss" group. To view this discussion on the web visit https://groups.google.com/d/msg/android-discuss/-/Y5Ys4212pmsJ. 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.
