Have you noticed the many tools to share your location? There's FourSquare and Gowalla, both about a year old. Then there are old-timers like Brightkite. And now, there's one that works with all three (and a couple more).
Check.in is a mobile application (currently in private beta) from Brightkite that, according to its home page, "takes the hassle out of checking in on multiple services." Most location sharing services take a a coffee shop, restaurant or other place and broadcast the spot to your friends so they can meet up with you. Using the APIs from the popular services, Check.in streamlines the process of using multiple services.
On one hand, this is a slick application that is a great example of integrating APIs. Yet some see Check.in as a sign that a different types of API--a federated standard--is really needed. We solicited feedback from both critics and users of Check.in and have compiled their responses below.
Reid Beels uses four services via Check.in:
"I've always viewed check.in as a features/time trade off... It bothers me to have to hit multiple services that offer nearly identical feature sets, just because my social graph is fragmented between them."
Dietrich Ayala wants nothing to do with it:
"It's a band-aid app for an ecosystem that requires n accounts to talk to all your friends... Federated approaches, such as the OpenMicroBlogging API, allow users to share data with friends across multiple services without needing to maintain accounts on each separate service."
Josh Babetski has been using Check.in since it launched. He thinks it is useful now and will continue to be:
"Much in the way a third-party eco-system grew out of creating Twitter and Facebook integrations, you'll see many players move to support social geo-social services as well. Let's not forget that Twitter is already expanding the ability to add place context and Facebook is moving that way. I think it's reasonable that you'll see a number of 'one-place, multiple check-in' services, like we saw with 'write once, post on many services.' Everyone will have their favorites."
Audrey Eschright warns against blindly consolidating:
"Either individual apps are no more than IM or email service providers, with location being the message we're pushing, or there are distinct differences between the services and what social contexts we use them in, and the idea of consolidated check-in makes as much sense as ccing your mom on an email about last weekend's drunken escapades."
Of course, it's up to individuals which accounts are integrated into Check.in, much as you might not choose to have your Twitter feed inside LinkedIn. There's certainly a precedent for Check.in's approach. We saw this occur with both bookmarks and status messages, most successfully by Ping.fm (our Ping.fm API profile).
"I consider this a bit of a hail mary for Brightkite. They still have a decent following, but they've lost the interest (and perhaps respect too) of their original geek crowd that they originally attracted, and they needed to get their check-ins back onto their service."
Brightkite founder Martin May told us they built it for their own use first:
"Lots of people told us they have been waiting for a service like this, and that we should release it to a broader audience. So we did."
What do you think of Check.in or services like it? How might APIs influence the future of location sharing?