Right.. the permission that shows up when I access account manager isn't as clear as the permissions when you first download the app. It strikes me funny that the ability to access the account manager is a manifest permission, but then you need to bother the user at runtime for yet another permission. Why not just make it part of the app installation permissions from the start.. although I suppose the answer for that is that most users won't know what it means at that time, so I am OK with that I suppose. I just wish there was a way to customize the permission popup that occurs so we could make it more app specific user friendly. It seems the only thing I can do is provide info in my description and hope users read it so they understand why my app is asking for that permission and what benefit they get from allowing my app to use it on their behalf.
On Tue, Jan 15, 2013 at 9:39 PM, Kristopher Micinski <[email protected] > wrote: > I don't see why this would necessarily be a bad thing: it's just part > of the security policy of the app. Of course, there's not really a > "let an app send email as me" permission, but you could imagine making > this as an app's configuration. > > (Of course, there is a permission that allows you access to accounts, > but it doesn't convey the same idea..) > > Kris > > On Sun, Jan 6, 2013 at 12:01 PM, Lew <[email protected]> wrote: > > Nikolay Elenkov wrote: > > > >> Kevin Duffey wrote: > >> > This article seems to indicate an XOAUTH2 with email.. going to give > it > >> > a > >> > shot.. but still can't find anything indicating that this is allowed > or > >> > supported. It would be good to find out if we can use the email > service > >> > without user intervention (except for the initial pop-up in the app > that > >> > asks for user permissions), or if google does not want apps to send > out > >> > emails on behalf of users using their gmail accounts even IF the app > >> > describes it and the user accepts. > >> > >> OAuth 2.0 is certainly not deprecated. You already have the link in the > SO > >> answer, but here it is again: > >> > >> https://developers.google.com/google-apps/gmail/oauth_overview > >> > >> Whether or not it is OK to use this in an app is another matter. > >> You should make it clear to users that you want to send email > >> from their account and give them an option to opt out. To make > >> sure the whole thing is legal, etc. hire a lawyer to draft your > >> terms of use/privacy policy, etc. Also make sure users > >> actually accept it before using the app. > >> > >> Disclaimer: IANAL, so take this with a grain of salt. > > > > > > And tell us the name of the app so I can be sure *NEVER* to use it. > > > > -- > > Lew > > > > > > -- > > 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 > > -- > 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 > -- 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
