On 08/29/2010 03:05 PM, Mark Murphy wrote:
[ Problems with permissions using Evernote as an example ]
What I'd like to see is:
4. Evernote makes READ_CONTACTS optional. Users see that READ_CONTACTS
is optional, and those who are concerned about it can go toggle it
off. Evernote adds an if() statement somewhere in its code to detect
whether the optional permission was granted and uses that to determine
whether to enable/disable the button/menu choice/whatever that
requires READ_CONTACTS.
Hallelujah! I couldn't have said it better myself - in fact, I did say
it quite some time age:
http://code.google.com/p/android/issues/detail?id=6266
(I experience almost identical concerns from users of some of my apps -
all of them being free and made in my spare time I'm not particularly
interested in maintaining several variations of them with various
amounts of permissions depending on user paranoia level.)
> [ Implementation ]
Thoughts?
You certainly have my vote. This is pretty much exactly what I've been
wanting all along. If there is any way I can help, I'd be *VERY* happy
to do so.
Best / Jonas
--
You received this message because you are subscribed to the Google
Groups "Android Developers" 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-developers?hl=en
