Social Networks, Phones, and Context

Speaking on a panel at IT Expo on Tuesday got me wanting to put down in written form some thoughts on how social networks and VoIP go together.

For decades, the phone was the primary way in which people communicated with their “strong links”. Now, there’s another and very different one, and that is the social networking sites. The kinds of activities people engage in on these sites is wild and wildly varying, especially as sites like Facebook have offered development environments to allow third parties to go wild with integrated applications. But the closest thing to a common denominator is that everybody is engaging in most of these activities together. That’s why they are on the social network in the first place - they are playing games with each other, forming clubs, exchanging messages, and so on.

So the natural question, and one which others have asked before, is how social networks and phones should begin to go together? After all, if you use both to communicate with your friends, and if phones offer personality, convenience of communication, and immediacy where social networks offer variety, convenience of activity access, and , there intuitively ought to be ways to combine the respective merits of each in useful ways.

Some people are already exploring this. Alec Saunders and iotum have their Free Conference Call application for Facebook; at myVox, we have our Voxcall widget, which lets people see when a page owner is online and invite the owner to a call. These are good, important first steps, but I think we all have to agree that they are precisely that: tentative, exploratory probes of the surface of integration.

To get really deep, you need a stronger link, with rich information flow both directions, between the phone and the social network. And a key element of that is the availability of context. Here’s an example:

Say Allan is on Facebook, and he’s flirting with Bel. Programmatically, we can recognize this because Allan is interacting with Bel through an app that describes itself as a “dating” app, or because of the particular actions he’s taking within an app, or even because of the words he’s using. He and Bel decide that they want to talk to each other. Allan picks up the phone. Because the phone is aware of the context, it:

1) preemptively asks Allan if he’d like to call Bel in particular;

2) when he says yes, automatically determines that this is a dating-related call from the above context;

3) automatically masks Allan’s caller ID;

4) shares with Bel’s phone that Allan is calling, and the context;

5) shares with Bel’s phone any other personal information that Allan is comfortable passing on, like perhaps a userpic;

6) shares the same with the Facebook, so its applications can react to the fact that Allan is calling, should there be cause to do so, and perhaps also indicating that Allan is on the phone and not available for other calls.

What we have here is a phone interaction that begins to stitch the social network and phone together. It takes advantage of context, tailoring the phone experience accordingly, and then passing back information to the social network “operating system” from which the network’s apps can benefit. And it’s a pretty basic example, really.

But the current state of affairs with consumer VoIP (the most likely phone-based starting point) is one where we are very far from being able to entertain this sort of thing. On the social networking side, many of the elements are there, though not the sort of generalized and standardized context info that would really help phone services to “read the mind” of the user. The real challenge is with the phone service, and with developing a dynamic caller experience that begins the moment you pick up the handset.

nick AT voodoovox DOT com

GM, VoodooLabs

VoiceMaps (or “even I can do it”)

One of the key goals we set for ourselves in developing the myVox API was to make it easy enough for me to use. I used to do software engineering, but have no formal training, and tend to hack code together rather than really engineer it. And I haven’t programmed with any regularity for years. So that gives us the Nick Test: if it’s too hard for Nick to work with easily, then it’s not good enough.

I think this proves the team passed the Nick Test with flying colors. It’s a Google Maps/myVox mashup I put together that lets you create a “voice map”. Basically, you can add pushpins to the map, then record voice for each pushpin. Click on the map to create a pushpin, then click the pushpin to add voice. If you return to a pushpin that already has voice, the recording will still be there.

It’s definitely a demo, not a finished product. There are so many great things that could be added to something like this:

• Persistence: If I leave the map and come back to it, the pushpins and recordings are gone
• Instances: Different users should be able to create their own maps and save them individually
• Photos: Combining photos and voice on a map would be very powerful
• Text: I should be able to put up text comments too
• Better controls: Right now, you can’t delete a pushpin from the page, or delete/overwrite a recording on an existing pushpin, and if you double-click to zoom, you end up also accidentally creating a pushpin
• Prettification: The info windows are a little clunky right now, and a better Javascript programmer could produce a slicker recording experience

But the point is that I, as a rusty and inexpert coder, was able to throw this together in just two hours, without any experience with the Google Maps API. That’s a testament both to the myVox API and to Google’s.

Take a look and see what you think. Want to make it better? We’d love to see your work. If you make a big improvement, post it to the $25K Developer Challenge… you could earn yourself some cash, too.

nick AT voodoovox DOT com

GM, VoodooLabs

3..2..1..Launch!

Here at HQ, we’re all very excited about the launch of myVox - but more than that, we’re really curious. What will people do with this thing?

See, we made a bet with ourselves about six months ago. The bet was that the wide world of developers would build much cooler things with our voice-recording tech than we would ever create for ourselves. Part of this is the straightforward parallel-processing proposition - there are way more of you than us - but there’s also the fact that you probably think and care deeply about topics and applications that are completely beyond our experience. If you check out our embryonic gallery, you’ll see applications like Blabberize that we just would never, ever have thought to build ourselves… and yet, having seen it in action, we can only shake our heads and wish we’d been that creative.

There are more Blabberizes out there, and we think the thing that’s been holding back their development has been access to fast, free tools for doing the voice recording bit. Phones are hard, phones take work, phones take hardware, and even though there are ways to get it done (we do love Asterisk, to give an important example), many developers have better things to spend their time and money on.

At least, that’s our bet. I hope you will prove us right.

nick AT voodoovox DOT com

GM, VoodooLabs