On 08/29/2010 03:23 PM, Mark Carter wrote:
On 29 August 2010 15:05, Mark Murphy <[email protected]
<mailto:[email protected]>> wrote:
3. Move READ_CONTACTS into some sort of plug-in/add-on APK,
[...]
Maybe have some generic READ_CONTACTS app (as opposed to each dev making
their own). I'm not sure how this can be done without introducing some
huge security hole though...
> [...]
In my app, I already have phone numbers (from READ_SMS) and only
additionally want the names for those numbers. READ_CONTACTS gives me
far more than I need and therefore far more cause for concern for my users.
I've been pondering this too for my apps, what I'd like to see is
something that just could call "pick contact" and the result would be
JUST the data related to that particular contact (for most cases, the
DISPLAY_NAME would be enough). Sort of like Intent.ACTION_INSERT_OR_EDIT
but in reverse.
I'd also like to see an API to which I can just hand over handling a
"badge" to. My app in itself has no need for all the user data as long
as I can just hand over a contact URI.
And while I'm at it: last I checked, Intent.ACTION_INSERT_OR_EDIT didn't
quite support all the (to me) obvious values for putExtras() - one of my
apps would be reasonably happy without being able to write to Contacts
as long as I could trust this intent to store all the provided data.
(This was a while ago, might have been fixed for 2.2)
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
