Business Internet Phone Service Blog

When Google does anything, it’s big news. First it was Google Voice, then it was Google Wave, and last week it was the new Gmail upgrade that allows users to call out to the PSTN. Let’s quickly go over some of Google’s existing ‘voice chat’ tools.

Google Chat/Talk is probably more commonly known as the built-in IM client in Gmail. It allows voice and video chats but is limited to PC-to-PC only.

Google Voice is more or less a fancy call forwarding service. Each user is given a US phone number, and inbound calls to that number are then forwarded to other numbers owned by that user. Outbound calls can be placed by dialing the Google Voice number or by using the provided web interface.

Google’s newest move combines the two. Gmail users will have noticed by now the new “Call Phone” option sitting at the top of their contact lists. Clicking on it brings up a dialing menu, and if you’re already subscribed to Google Voice, your Google Voice number will be used for outbound calls. Your Google number can also be set to forward to your Gmail account so that you can take calls there as well. Additional features like free voicemail transcription and personalized greetings are also included.

I signed up for a Google Voice number to give this Gmail calling add-on a try. The sound quality isn’t half bad if you’re using a headset, and the added convenience of being able to call anyone I want when I’m browsing my e-mails is pretty neat. I’m also enjoying being able to listen to voicemails as they are left, and having the option of jumping into calls when I want to. For voicemail transcription, I would much rather go with Phonetag. Some of Google’s transcriptions are ridiculously inaccurate.

This is all pretty cool, but I’m not sure that it’s anything beyond that at this point. The service itself hasn’t really changed since Google Voice launched last year—I mean, calls to the US and Canada using Google Voice were always free, weren’t they? Bringing Voice functionality to Gmail seems to me just a move to get people like me who never bothered with Google Voice to actually try it. Mission accomplished, if that’s all they’re after.

Industry experts have been busy doing their usual speculating. Some say that Google is establishing the groundwork for their upcoming Facebook competitor by increasing engagement in their already existing social networking tools (Currently, you have to have your Gmail open to be able to take incoming calls forwarded from Google Voice). I’m not completely convinced here. First of all, the calling feature probably will not make me want to use Gmail more than I already do—it’s an added convenience that I might use every once in a while just because it’s there, and not really something that I see driving conversions. I’m not going to be on Gmail more to wait for incoming calls—I already have this thing called a phone. Secondly, Facebook has toyed around with the idea of introducing calling, and I’m pretty sure they dropped it. One-on-One calling is a bit too personal for most interactions that take place on a social networking site, which is probably why you haven’t heard much about the already existing Facebook calling applications.

Others say that this move by Google is a direct assault on Skype. While this may be true, the current product isn’t really a Skype killer and it kind of makes sense that it’s not all there yet. I could see how they might use Gmail, one of their more successful services, as a litmus test for new product offerings. On the flip side, I also probably wouldn’t read too much into the 1 million calls made in the first 24 hrs (Take into account how many Gmail users there are and the fact that I alone made like 10-15 test calls).

The last popular idea is that Google is really just after better advertising data. With more Google Voice users comes more voicemail (and maybe even conversation) transcriptions, which leads to more targeted ads. All I have to say to this is, good luck trying to make sense of some of these:

10GUI is something I came across almost a year ago that I was reminded of the other day while speaking to John about touch screen devices. Designed by R. Clayton Miller, 10GUI is a concept design in the next evolution of human interface elements. He says, "the mouse and the windowed desktop are perhaps the two greatest innovations in the history of human-computer interaction. But like all innovations, they are best seen as part of a continuum rather than a terminus."

When I first saw the video I thought the designer's proposals to change the common desktop environments were very intriguing. The end result is something pretty impressive in its use of natural hand motions to bring the tactile manner in which we interact with our everyday surroundings into the virtual realm. Even more impressive than the use of touch is the reorganization of the desktop software to fit the mode of interaction. Fortunately for 10GUI and other UX proposals like it, the hardware is becoming more ubiquitous in the market by the day with the advent of touchscreen devices like Apple's multitouch environments. However, unlike the touchscreen devices like the iPad that get to define a whole new niche and thus get to define the landscape, the 10GUI and its counterparts are attempting to replace and directly compete with a "good enough" working model, the mouse. Defeating the mouse is going to be the largest obstacle to the 10GUI and other UI/UX proposals like it. As in other evolutionary trends, the success of the 10GUI will hinge on it proving itself so far superior to the current model that the idea of the mouse being "good enough" dies out.

This is much akin to the current barrier we have in proliferating the adoption of hosted SIP over the established "good enough" solutions like the PSTN and on premise PBXs. We like to think of the benefits of hosted SIP are like those of email, IM, or other web technologies; you don't need to pay a separate bill, you use your existing Internet connection and let the end devices interpret the data, you can take it with you wherever you go, the data can integrate into other systems, yadda yadda yadda. Unfortunately for SIP however, email, IM, and web really had no existing mainstream competition when they came to town, so the adoption rate was not hindered by a "good enough" alternative. On the contrary, Google Wave was recently killed because it failed to convince people that it was so far superior to email and IM that the world should switch. Back to OnSIP, our challenge in making it the new norm is to show the populace that the benefits the service brings so fare outweigh the potential of the existing "good enough" solution that there isn't even a fair fight between the two. Here is to hoping that Wave was just ahead of its time, while hosted SIP is long overdue.

Anyway... enjoy the video:

Prior Posts

I’ve thought long and hard about the proper role for a CEO. At Junction Networks specifically, the main focus of that role has changed over the years, but I like how Fred Wilson puts it at the AVC.com blog:

“A CEO does only three things. Sets the overall vision and strategy of the company and communicates it to all stakeholders. Recruits, hires, and retains the very best talent for the company. Makes sure there is always enough cash in the bank.”

It's back to school time around here, a time when parents breathe a sigh of relief and teachers do just the opposite. In the back to school spirit, here is an entertaining auto-attendant message for a high school in Australia.

Supposedly, this message is a statement to the community parents who had put the school under fire for their attendance policy.

This post is by Mike, CEO of Junction Networks

Over at the American Express OpenForum site, Guy Kawasaki wrote an excellent post about how too much money can be a bad thing for startup companies. Ed Sim who runs the Beyond VC blog wrote a similar article back in 2006, which I've kept bookmarked.

This blog is by Brian, Software Engineer here at Junction Networks. This is a good read about adapting a product to the iPad; it contains some tips for developers and is the first of a series Brian will write about updating my.OnSIP for the iPad.

Previously…

In the previous installment of this series, I mentioned that audio in my.OnSIP wasn't working on the iPad. In this installment, I'll go over the issues and workarounds.

We've hit an important milestone here as depicted in this photo from my office yesterday. I wonder if anyone can tell. A little help with some of the artifacts in this photo:

Polycom phone: No, we're not celebrating our acceptance into the Polycom Field Verified Partner Program. That happened last year.