I didn't expect lots of positive feedback from developers, I rather would have liked some feedback to make the app accepted also by devs. Instead, I mostly read comments about how bad it is to show to users what data an app has access to.
I'm still happy since I understood that it might not be that clear that my app shows a potential! danger level, it does not show how dangerous an app actually is. That is also not my purpose. I'll try to solve this issue. About strategies of requiring permissions that will be used in the future, as a dev, you might require as many permissions as you like, but you cannot expect users (like myself) to ignore all of them if I don't see the point about requiring access to whatever private data. Deal with that. I really appreciate transparency and I want my (even if few) users to know why I'm reading their data. I would like all apps to be transparent about privacy, but it is not the case! That's why Apprivacy was released. I thing the model of keeping permissions related issues as hidden as possible won't work out in the long run. I also think that a more transparent approach would help in letting users know about the security model of Android, and so users might become less reluctant in updating apps which require new permissions. -- You received this message because you are subscribed to the Google Groups "Android Discuss" 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-discuss?hl=en.
