Ok, just to add a little more clarity: During installation, the list of permissions required by the app will be shown to the user. (like how it is now) But there will be a check box next to each permission. So the user can grant/reject individual permission.
Thanks KC On Feb 13, 2:37 pm, Keshav Channa <kbc.cha...@gmail.com> wrote: > I have a suggestion for the Android design group. > I'm not sure how viable it is, but here it goes. > > Right now, when someone installs an app, they see what are the > permissions that the app requires. > Looking at that, a decision has to be made whether one wants to > install the app or not. > (Frankly the user is helpless here, and the answer is binary - yes/no) > > For example, while I'm installing, some times I see apps that DON'T > need to access my phone/sms data having permission for that. Why is > that so? I've seen some games do this also. > > Instead of the app deciding permissions, let the app request the > permissions that it needs. > During install time (or at any other time using the "Settings" app), > the user can choose to approve/disapprove permissions. > > That way if I'm not comfortable with a certain app, then I'll probably > NOT give it sensitive permissions. > > On the other hand, the apps need to handle a particular permission > being granted or not by the user. > > But from the end user point of view, this makes sense. > > Thanks > KC -- 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+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
