bradmccarty

Volunteer-based nonprofit that has already saved one life. "Our raiding parties (volunteers) give their time, energy, and care to provide support, practical help, wellness guidance, and social connection. We’re here because cancer should never feel like a solo battle."

The problem with this actually is the LinkedIn API. LI has restricted it so heavily that you can't use the API to export data - http://thenextweb.com/dd/2015/02/12/linkedin-takes-aim-devel...

The only alternative is to apply to the Partner Program, which will likely be denied given LI's history.

Hi Mike.

We're always happy to see more companies set up shop in this space. It helps to keep us on our toes.

At first blush, it seems that EveryoneAPI is focused primarily on phone numbers. Conversely, our focus with FullContact is much more in line with social profile and public social data. Though you certainly can query the FullContact Person API via a phone number, that's never been our primary focus.

With relation to the comment about speed, it's worth noting that greater than 95% of Person API queries are returned in 30ms or less. But to the end user, depending upon where they are hosted, network latency can play a large role in the actual response time, which is a factor for any http based API traffic.

Like EveryoneAPI, we prefer to compete on merit rather than slinging mud. If you have a project that you're building, I'd love to see how we can help. Our APIs are always free to get started, so you can see your results before ever having to pay.

Stay tuned ;)

Hey Doug -

We love Vibe. It's a great app and carries a lot of the same features. I think that the advantage of using FullContact for Gmail is being able to interact with your FullContact address book, and then automatically sync that information back to your Google Contacts. But ultimately, it's whatever works best for you. We know that the Vibe team shares our passion for making you awesome with people, and we're happy that they're making great products.

iOS and Mac apps are coming next, while we perfect Android compatibility. We're also working on contact sharing among accounts. It's our biggest request, and we want to make sure it's right. As for social networks, we already integrate with a number of them. What would you like to see?

We're definitely looking at it.

For good reason. We love(d) Rapportive before LinkedIn neutered it. But we knew that it could be better.

Out of curiosity, there's a Labs function that you can use to enable right side chat. Would you be using it by chance?

http://d.pr/i/1lA4M

Interesting. We'll take a look at it. Thanks for flagging it up!

It's a pretty exciting day for us, and we'd love to get your feedback.

CardMunch still (for the next few days anyway) uses real people. That didn't change when the company moved under LinkedIn. Unfortunately there was an opportunity there that was never really seized.

As for how we compare? That's a matter of personal preference.

While I like Evernote a lot, and use it daily, it's just not where I want to store my contacts. Nothing about that makes sense to me. My contacts need to be where they're the most accessible, from the device that I'm going to use to get in touch with them.

I don't use a CRM, but if I did, I'd want to scan cards into it because that's where it makes sense for those contacts to live. I'd want to segment them and I'd want to pull them into my phone when I needed them. None of these things are easy to do when you use Evernote as your repository. It's great for being your "second brain", but not so great for being your phone book.

The big thing to mention here is that we don't use OCR, we use real people. It's the main differentiator (aside from the Zapier integration) between Card Reader and just about every other alternative. Yes, it's slower, but it's also incredibly accurate. And really, when was the last time that you scanned in a business card and needed the information from it 20 seconds later?