Agree, click-to-call would be awesome. We're actually launching Google
Contacts integration into private beta this week, which includes
pulling phone numbers out of Google Contacts and showing them in the
sidebar (we only show them to the owner of the address book, of
We won't be passing phone numbers to Raplets by default, but in a case
like yours it would make a lot of sense. I'd like to work out a
protocol for Raplets to request different contact fields (other than
the current default email address, name and Twitter username).
> You received this message because you are subscribed to the Google
> Groups "Raplet developer discussion list" group.
> To post to this group, send email to raple...@googlegroups.com
> To unsubscribe from this group, send email to
> For more options, visit this group at
Yes, OAuth is one way we could go — although it's more geared towards
situations where the requests are initiated by the client application.
In our case Raplet requests are initiated by Rapportive itself, so the
same protocol may not apply.
We're already using OAuth the other way round — for Rapportive to
request access to a Raplet.
Sent from the Verizon network using Mobile Email