I think I see where you are coming from to a point however honestly I dislike the global statement. I mean a wall of permissions is going to turn into white noise to users (in which case the permission could be for Brick for all they care leading to spam) or paranoid users (in which case your platform dies from no use, but is perceived as lack of creativity from developers). I am just saying it would be nice, from a user perspective and from a developer perspective if I could optionally request a permission and/or upgrade to a permission via user interaction (through a system UI that could persist a No or a Yes). I mean if it's at install time, how do you explain to a user why the permission is needed (They aren't engineers remember, and it's only like 256 characters in the market description field).
Just my two cents. On Aug 27, 9:45 am, Dianne Hackborn <hack...@android.com> wrote: > No it must be done at install time. Honestly, this is better than prompting > the user all over the place when they are actually trying to do some other > task -- they are more likely to look at permissions (and as a whole) when > the task at hand is installing an app. > > You can't intercept URIs without going through a system UI where the user > decides what to do. Also at that point the task they are doing is "look at > this thing I selected," so the decision they are making (pick which will > show the thing they are wanting to look at) is relevant to their task at > hand. > > On Fri, Aug 27, 2010 at 9:34 AM, Greg Giacovelli <miyamo...@gmail.com>wrote: > > > > > > > I suspect there has to be. I mean I saw for bluetooth there is. I was > > wondering why it is not as easy for the other permissions. I mean heck > > we can intercept urls without even asking a user for the most part, so > > I would have to suspect that permissions have to have this ability. > > > -Greg > > > -- > > 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<android-developers%2Bunsubs > > cr...@googlegroups.com> > > For more options, visit this group at > >http://groups.google.com/group/android-developers?hl=en > > -- > Dianne Hackborn > Android framework engineer > hack...@android.com > > Note: please don't send private questions to me, as I don't have time to > provide private support, and so won't reply to such e-mails. All such > questions should be posted on public forums, where I and others can see and > answer them. -- 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
