Jay-andro wrote:
> I would ideally like an
> android api that protects this info and just allows my app to invoke a
> sendmail method with subject, body etc. Under the covers the api would
> access the personal account credentials of so it can connect to the
> smtp server.

As a user, I would find this completely unacceptable. But, that's just me.

> Second, consider the following use cases where this requirement comes
> up:

Those cases all require you to send emails. You can do this today. You 
need to get yourself a Java JAR that supports SMTP, ask the user for 
SMTP credentials (server, from address, SMTP authentication settings, 
etc.), and you're set.

I can see the argument that it would be nice to have an option where the 
user didn't have to configure that email information again. However, 
please understand that under no circumstances you should be assuming 
that the user *wants* you to use the pre-configured account for any of 
these situations. Hence, you're going to need to support allowing the 
user to specify alternative SMTP credentials, anyway.

Long term, I can definitely see where Android might evolve a 
general-purpose email service, where the user can create multiple 
accounts, and it is easy for applications to allow the user to choose 
which of those accounts to use (or launch an activity to define a new 
account, etc.). However, as with any open source project, how long the 
"long" in "long term" is depends on who all has itches and decides to 
scratch them.

-- 
Mark Murphy (a Commons Guy)
http://commonsware.com
_The Busy Coder's Guide to Android Development_ Version 1.9 Available!

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to