On Wednesday, August 15, 2012 2:36:16 PM UTC-7, omoling wrote: > > 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.
With all due respect, you need to improve your listening skills. Despite all of our hostility, you have received five or six helpful suggestions in this thread. You are free to ignore them if they are not what you wanted to hear, but they are there. Some suggestions involve taking away a feature that you have already spent time on coding, but that is still a positive suggestion. Even Tim's suggestion of "Find another niche" was a positive suggestion with your best interests at heart. > 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. > At least you have listened to one suggestion. Take away the "Express doubt about this permission" feature, and your app will be even better. 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. > Adversarial statements like "Deal with that" and you wonder why you are having trouble getting positive feedback. Several experienced developers have tried to explain this to you, but you insist that READ_LOG is unnecessary and evil nonetheless, and insist on saying so to your users. Why should we give you more feedback if you are not listening? Just try adding READ_PHONE_STATE after you have 50,000 daily users because some ad network requires it. I dare you. Let us know how it goes. > 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. > Transparency, huh? Do you have a definition of transparency? Here is a suggestion then. You can scrape the Market and determine which apps have a stated privacy policy url. If it is null, mark the app as NON TRANSPARENT. If it has one, mark it as TRANSPARENT, and allow the user to click through to the policy. Do this instead of the danger level and expressing doubt, and your app is done. Nothing to add. Nothing to take away. It delivers on its promise, and won't offend any developers. Nathan -- 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/-/jPVoA4S4DJAJ. 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.
