Google Voice
Latest
Access Google Voice from the iPhone via Safari
Earlier today, Google made a mobile web version of Google Voice available for the iPhone. To understand the significance of this move, here's a bit of back story. Apple pulled all Google Voice related apps from the App Store back in July, which led to an FCC inquiry, which led Apple to claim they had not rejected but were "studying" Google Voice, which Google contradicted. The biggest surprise in the whole scenario is that AT&T said that they had no problem with Google Voice on the iPhone. Months later, there's still no official Google Voice app in the App Store. You can view the long version of the story here. The mobile web version announced today (iPhone 3.0 required), while not the first, utilizes HTML 5 to accomplish some new and impressive tasks. For example, it lets you display your Google Voice number on outgoing calls and provides easy access to voice mail plus text messaging (send and receive). Additionally, you can dial with the virtual keypad and read transcripts of messages. It's not all roses, of course. For instance, it won't access your iPhone's contact list or push incoming SMS. Unless they're going to limit the capabilities of the iPhone's browser, or somehow block access, there isn't much Apple can do to prevent users from trying it out. Note that this is limited to the US. To try it out, point Mobile Safari to http://m.google.com/voice. Pro tip: Add a bookmark to your iPhone's home screen to launch with a tap. [Via ZDnet]
Google Voice comes to iPhone and webOS, as a web app
FCC investigation be damned, Google has finally managed to bypass the App Store and release Google Voice to the iPhone (and webOS, too) the same way it pulled off Latitude, i.e. via a HTML5-based web app. According to Senior Product Manager Vincent Paquet, it should work with any HTML5-compliant device, although the formatting at this point has been tailored to Apple and Palm's platforms. So here's how it works: much like with its mobile Gmail site, the app caches your contacts list in a browser page. All the usual GV functionality is there, writing SMS messages, checking your inbox, and even listening to voicemails (although that latter functionality wasn't working for us yet in our trials). Placing phone calls is an interesting trick: as pictured above, after you choose the recipient, the app prompts you to call one of Google's local numbers via the native dialer -- even for international calls, hence the lower rates by paying through Google. The recipient will see your proper GV digits, and upside with this method is you'll still be able to utilize call waiting and background usage. The catch, of course, is a call history littered with random numbers. It's not a perfect solution by any means -- if anything, take solace in an assortment of home screen icons for each section of the app -- but it's probably the best we're gonna get for the time being. The page should be up and running later today, so if you're anxious, direct your mobile browser to voice.google.com and just keep hitting refresh. %Gallery-83907%
Clean out those ears: Ooma's Telo goes high-definition, gets iPhone app
The home entertainment world may have moved on from high-definition everything to 3D everything, but the telco industry is a little bit less bleeding edge, just entering the HD revolution now courtesy of Ooma. The Ooma Telo is getting upgraded and will soon be packing some tidy new features including so-called "Pure Voice" and "High Definition Voice" enhancements, promising to deliver "crystal clear conversations over congested networks" and a "richer, more natural sounding conversation." Also on tap is direct support for calling through Google Voice, Bluetooth support so calls to your celly can be piped through your Telo, and "human-aided" voicemail transcription that we can only assume means some low-wage worker gets to listen to every reminder from your husband or wife to pick up some milk on the way home. Now there's a career opportunity for nosy folks. Full PR after the break. Update: Updated the image to reflect the new Telo.
Is Google Voice available for the iPhone?
Need a refresher on the Google Voice and Apple saga? Let's recap the story to date: Apple pulled all Google Voice related apps from the App Store back in July, which led to an FCC inquiry, which led Apple to claim they had not rejected but were "studying" Google Voice, which Google contradicted. The biggest surprise in the whole scenario is that AT&T said that they had no problem with Google Voice on the iPhone. Yet here we are, 4 months later, and still no decision (that we know of) has been made. I've previously referred to this as Apple's pocket veto of Google Voice where they are able to say they haven't rejected it when they have, in effect, rejected it. Put it all together, and this has led me to put up a website for your "Google Voice on iPhone" questions, which I narrowed down to IsGoogleVoiceAvailableForTheiPhone.com? As it stands today, the answer is a qualified "No" in that there are no Google Voice apps available from the App Store, but I was curious to see what options are available. I found three tools that you can use today, and one more which is on the horizon.
Should we continue using an app that Apple has rejected?
It doesn't happen so much anymore, but not too long ago you'd hear about a new offering arriving in the App Store that would stir up a little controversy (the NetShare tethering app springs to mind). They'd enjoy some fanfare and a ton of purchases for a few days before being summarily removed, never to return and often without a thorough explanation from Apple. A relatively small number of users would retain possession of the app and would take a bit of pride in knowing that they were in the right place at just the right time to snag a copy of the app before it was yanked. When I got the email from our very own Mike Rose regarding the release of GV Mobile, I was pretty excited. I'd been wanting to more fully adopt the Google Voice service, but had wanted a more iPhone-ish experience in doing so and GV Mobile seemed to have just what I was jonesing for. I paid the three bucks right then and, like The Giving Tree, was happy. My adoption plan for Google Voice didn't pan out quite like I'd hoped for a while after that. I'd use it occasionally, but I had trouble moving it from the number I gave to sales people to the number I gave to my mother-in-law. But, despite the absence of the app in the App Store, I still had a perfectly working copy of it on my iPhone, ready when I was - or so I thought. A couple of weeks ago, I had decided that it was time to make Google Voice a more central part of my communication workflow. Having not launched GV Mobile in a while, I fired it up to reacquaint myself with the interface, capabilities, etc. Trouble is, I couldn't authenticate with Google. I triple-checked my credentials but the app would just throw an error on launch and that was that. A couple of people on Twitter had mentioned having the same issue and a quick Google search informed me that, sure enough, the app no longer worked. Apparently, Google had modified the Voice API such that authentication now worked differently than it did when GV Mobile was written. Because the app no longer had Apple's seal of approval, I had little recourse because there obviously weren't going to be any updates to the app anytime soon. Which raised the broader question - how heavily should we rely on "orphaned" apps? If they're self-contained (which is to say, they don't rely on any web sites or services to function properly), it probably isn't a big deal, but if you're a heavy Google Voice user and GV Mobile is how you got your work done, is it really a good idea to hang your hopes on an app that will likely never see any type of upgrade or bugfix release? I can confidently say that this little hiccup has seriously cramped my plans for more completely adopting Google Voice. Is the same true for you? Have you experienced this type of dilemma with any other now-missing App Store purchases? Tell us about it in the comments!
Google makes Gizmo5 acquisition official, offers few details
This one wasn't exactly the best kept secret of the week, but Google has now come out and officially announced that it has acquired VoIP company Gizmo5, and that Gizmo5's engineers will expectedly be joining the Google Voice team. This being Google, however, it isn't saying much more than that it's looking forward to "working together to bringing more useful features to Google Voice," although that's no doubt more than enough to make the folks at Skype have a slightly less relaxing weekend. Current Gizmo5 users can also expect their service to continue as normal, but Google has suspended new signups "for the time being," and existing users can no longer sign up for a call in number.
Google to acquire Gizmo5, swing at Skype with VoIP-enabled Google Voice?
There's no official word on this yet, but the inimitable Michael Arrington says that Google's up and purchased VoIP company Gizmo5 for "around $30 million in cash." You know, pocket change for the crew in Mountain View. The deal would presumably bring Gizmo's SIP-based VoIP talents to Google Voice, taking it from quirky phone-management service to complete end-to-end calling solution, and instantly catapulting it into direct competition with Skype. Heavy stuff -- we'll see if Google or Gizmo5 confirms Mssr. Arrington's report sometime soon.
Trillian's 75-day limbo: the App Store, Freewill, and the pocket veto
What do United States politics, a Canadian rock song, and a California computer company have in common? Here are some hints: the Pocket Veto, Freewill, and the App Store. When the President of the United States is presented with a bill, she or he has 10 days to sign it, or veto it. If the President does not want to be seen as having acted in favor of or against some particular piece of legislation, he or she can simply put it in a pocket and wait for the clock to expire. Or, as the Canadian rock band Rush once said: "If you choose not to decide, you still have made a choice." Back in late August, Apple claimed not to have rejected the official Google Voice iPhone application. The company claimed it was still "studying" it. Around that same time, Cerulean Studios submitted the amazing-looking Trillian for iPhone instant messaging application. Over two months later, Apple has not taken action on either app. Neither app has (officially) been rejected, but they have not been accepted, either. In the case of the official Google Voice app, it feels very much like Apple has simply "pocketed" the application.
Google says it's now blocking 'fewer than 100' numbers in Google Voice
The crux of AT&T's recent complaint to the FCC regarding Google Voice was that Google -- not being subject to the common carrier rules that help facilitate fair, open telephone networks -- was blocking customers from accessing numbers managed by rural carriers that charged higher connection fees, thereby giving it a leg up on its Old Guard competition by saving cash in ways AT&T and others are legally barred from doing. Google's hitting back today, not by agreeing to submit to common carrier rules (come on now, don't be ridiculous) but by saying in a statement to the FCC that it's now blocking calls to "fewer than 100" numbers in total now that it has finished implementing new back-end capabilities that allow it to single out specific numbers rather than entire exchanges. Google complains that calls to the top ten exchanges accounted for 26 percent of its entire connection fee outlay -- but yeah, that's pretty much what telcos have been dealing with since time immemorial, so the bellyaching's likely to fall on a lot of deaf ears. For what it's worth, the company is still asking the FCC to make sweeping changes to connection fee policy, but whether this ends up getting them out of AT&T's more immediate concerns remains to be seen. [Via Phone Scoop]
Google Voice can now manage your cellphone's voicemail (video)
You read that headline correctly, Google Voice now works with your existing mobile phone number -- no need to choose a new Google number that must be communicated to friends, family, and co-workers. This "lighter" version of Google Voice then lets you hand-over voicemail responsibility (and your data) to Google's authority where you can listen to (or read via automatic voice to text conversion) your voicemail on a computer in any order you like, read them as text messages on your phone, and choose personalized greetings by caller. A side-by-side feature table that compares Google Voice when choosing a Google number versus your existing cellphone number can be found after the break. We've also dropped in a cutsie video overview of the change -- surely a company that produced it can't be evil, can it?
Google Voice voicemails appearing in public search results
We're not exactly sure what's going on here, but it certainly seems like at least some Google Voice voicemails are being indexed and made publicly available somehow. If you punch in "site:https://www.google.com/voice/fm/*" as a search string you get a few pages of what appear to be test messages, with a couple eye-opening obvious non-tests scattered in there as well. Dates on these messages range from a couple months ago all the way until yesterday, so this is clearly an ongoing issue -- hopefully Google patches this up awful fast. P.S. - Google Voice transcription accuracy really falls off a cliff when it's listening to muffled audio, doesn't it? Update: Google says it's changed how shared messages are indexed and made available to public searches, so we're hoping this was just a one-time thing. [Via Boy Genius Report]
Business Insider: AT&T to allow VoIP on its 3G network
Business Insider is reporting that AT&T has given Apple the go-ahead to enable Voice over IP (VoIP) apps such as Skype on its 3G network. In the past, VoIP apps required a Wi-Fi connection. The announcement was made in advance of the annual conference sponsored by CTIA - The Wireless Association. AT&T Mobility CEO Ralph de la Vega is scheduled to give a keynote at the conference tomororw and could use the event to further elaborate on their intentions.The announcement is most likely a response to recent events at the Federal Communications Commission (FCC), which is proposing new rules that would prohibit carriers from blocking apps on their networks. A public announcement by AT&T stating that they will allow apps such as Skype on their network would remove any doubt that it's the company that is doing the blocking, and put the spotlight firmly on Apple to explain why they're not approving VoIP apps. As noted yesterday, VoIP provider Vonage has made its app available in the App Store, although ratings after the first day probably make them wish they hadn't...It should be noted that the announcement will likely have no bearing on the fate of Google Voice, which was rejected by Apple on the grounds that it duplicates functionality already found in the iPhone. The Google Voice app allows users to control their Google Voice account, send SMS messages and check voicemails, but does not provide any VoIP functionality.
Verizon plans to support Google Voice, will launch two 'game-changing' Android devices in coming weeks
We're currently on a press call with Verizon CEO Lowell McAdam and Google CEO Eric Schmidt to discuss their new partnership, and while it's mostly a love-fest between the two with no real announcements, there's been some interesting tidbits. First off, Verizon will be launching two Android products in the coming weeks -- we'd say at least one of them will be the Motorola Sholes, and while the other is still a mystery, Google says it'll be "game-changing." Very intriguing. Second, and perhaps much more interestingly, Verizon's making a big push to be seen as the "open" carrier, and flatly stated that they'll be supporting Google Voice on their network: "Either you have an open device or you don't." That's a big change for Big Red -- just remember that a year ago Google and Verizon were still at each other's throats over 700MHz open-access rules. Now? Rainbows and kittens all around. Lastly, there will be a major app push coming from these two -- Verizon's obviously going to preload Android Market on its devices, and there should be some 10,000 apps available when all is said and done. Not a bad show of support by Verizon, we'd say -- and there was a lot of talk about long-term roadmaps and a "family" of products, so we'd expect much more than just two phones and smiles over the next few months. Things are certainly getting interesting, no?
Using Skype to battle cell phone dead zones
Is the cell coverage in your area not up to par? Whether you happen to have steel walls or live where there are no cell phone towers or trees cleverly disguised as cell phone towers, some of us must deal with the reality that, while we own arguably the most innovative gadget in recent years in the iPhone, we may not have had the best carrier to accompany it. One way to address this "bag of hurt" is through the Skype [iTunes link] app. If you don't already have the Skype app, download it -- it's a free download in the App Store. Next, you'll need to make sure that Skype stays online when the screen is locked. This is accessible via the Skype app preferences within the iPhone's main settings page. After this is enabled, the Skype app continues to run in the background and maintains a Wi-Fi connection even after the sleep/awake button is pushed -- or if it's set to automatically lock after a given time interval. Second, because Skype requires a Wi-Fi connection to make and receive calls, you'll also want to make sure that whatever cell phone dead zone you're at also happens to have a Wi-Fi connection. This workaround obviously isn't without its weaknesses. Assuming that most of those calling you would prefer dialing a phone number instead of your Skype user name, you'll likely need a separate phone number. One option is SkypeIn, which marries Skype to a real phone number. The service costs $18 for three months or $60 for a whole year. And if you happen to have a Google Voice phone number, directing your calls to your SkypeIn number is an option. Alternatively, you could forward all of your iPhone calls to said Skype number whenever you anticipate a cell phone dead zone -- say, before you enter your house, if you have bad reception there. This is accessible via the Phone preferences within the iPhone's main settings page. Doing this, you won't have to give out multiple numbers to your friends and family. One of the other drawbacks of this alternative is that while an audible indicator (a ringing noise) is present when you're receiving a call, a visual one isn't. In other words, you may need some cat-like ears to know when you're receiving a call. A seamless solution this is not, but it nonetheless provides a possible workaround until more cell towers are built in your area, or until a push-based solution is available for Skype. Readers, tell us what you're doing to remedy cell reception issues. Be it a do-it-yourself tin can signal booster or anything else, let us know what's worked for you.
AT&T, Google trade barbs over Google Voice while FCC listens in
AT&T filed a scathing letter with the FCC earlier today complaining that Google's exhibiting a blatant double standard with Google Voice by blocking customers' access to numbers hosted by carriers that charge higher interconnect fees -- something that's specifically forbidden for traditional telephone carriers under so-called common carrier laws. The argument essentially revolves around the fact that Google's move helps it compete unfairly against AT&T and others by arbitrarily blocking calls to numbers that'd cost it too much to connect, which AT&T says puts Google in an "intellectual contradiction" given its "noisome trumpeting" (ouch!) of support for net neutrality. It is pretty interesting that Google wants a free, open internet with the left hand while it's blocking certain telephone calls with the other, but Mountain View wasted no time in responding to the communication, posting an quick blog piece where it says there are "many significant differences" that should exempt it from common carrier legislation (some sound reasonable, though the argument that "Google Voice is currently invitation-only, serving a limited number of users" makes us think they're digging pretty deep to come up with reasons they shouldn't have to pony up the cash to get these calls connected). If there's a bright side to the bickering, it's that both AT&T and Google can agree on one thing: rural carriers' continued ability to charge high connection fees hurts everyone -- it's a "badly flawed" system, in Google's words, and it'd be great if the FCC would do something about it. Whether this whole spat ultimately influenced the outcome of the Google Voice iPhone app debacle is unclear, but it's obvious that AT&T's been stewing about this for a while -- so let it all out, guys, mommy FCC's here for you, and one way or another we suspect GV's going to have to end up going legit if it wants to grow its user base by any significant measure. Check out the gallery for AT&T's letter and follow the read link for Google's shorter, slightly less aggressive response.
Google contradicts Apple, states Apple rejected Google Voice
The Google Voice story grows even murkier today as new details arise about its App Store rejection. When the FCC launched an inquiry into the presence of the Google Voice app on the App Store, Apple, AT&T and Google all provided formal response letters. Portions of Google's letter were kept confidential from the public. Today, after several requests, Google finally released their entire FCC letter to the public. In it, Google states that Apple did in fact reject the Google Voice app for the iPhone, and that Phil Shiller met and talked to Alan Eustace at Google about the rejection. Google's letter contradicts what Apple has stated, that they never actually rejected the Google Voice app. Today's news adds another element to the disappointment and confusion over the presence of Google Voice on the iPhone. Apple stated to Engadget that they did not reject Google Voice and that they continue to look into bringing it to the App Store. TUAW has contacted Apple for a further statement about the rejection details. We have not heard anything back yet. [via Engadget]
Google says Phil Schiller himself rejected Google Voice from the App Store
It was always curious that Google's response to the FCC inquiry about Google Voice and the App Store had been redacted, but now we're starting to see why -- El Goog and the FCC have just released the full text of the letter, and it flatly contradicts Apple's take on the matter. If you'll remember, Apple claimed that while Google Voice hadn't been approved, it also hadn't been rejected, and that its status was in limbo while the folks in Cupertino "studied" the matter. Not so, says El Goog: according to its letter, Phil Schiller himself told Google that GV had been rejected on July 7 for duplication of functionality, following a similar conversation on April 10th during which Schiller rejected Google Latitude in part because it might "offer new features not present on the preloaded maps application." Yeah, that's a huge discrepancy, and it makes Apple's version seem even more divorced from reality that it already is. Things are starting to heat up -- we'll see what the FCC makes of all this. Update: And here we go -- Apple just pinged us to say the following: "We do not agree with all of the statements made by Google in their FCC letter. Apple has not rejected the Google Voice application and we continue to discuss it with Google." Update 2: So we've been thinking about it, and here's our question -- if Apple didn't reject GV, and is still studying it, what exactly did Phil Schiller say to Google to make them think it had been rejected? The difference between "rejected" and "on hold pending further discussion" isn't a subtle one, and Google clearly thought GV had been explicitly rejected. For whatever it's worth, reports of GV's "rejection" are how this whole mess got started, so either this is all one huge misunderstanding, or someone here isn't telling the entire truth. Read - Google unredacted FCC filing [Warning: PDF] Read - Google Public Policy Blog explaining decision to release letter
FCC makes it official: Cellular carriers policies getting a closer look
Maybe the submissions by Apple, Google and AT&T helped, or maybe they hurt, but the FCC is going to take a closer look at the U.S. cellphone industry and if competition is helping consumers. [Link to FCC announcement in PDF format] Today the Commission said: As communications technologies and services become more essential, and the communications market more complex, information is key to consumer protection and empowerment. The Commission seeks comment from communications service providers, academic researchers, consumer groups and third-party analysts on how best to ensure consumers have the information they need to make informed decisions in the communications marketplace. The FCC has been particularly interested in the Google Voice app for the iPhone, which Apple has said is still undergoing scrutiny. The FCC has questioned AT&T about whether or not it advised Apple to not approve the app. AT&T has denied it had any say. AT&T has admitted it is wary of apps like Slingbox Mobile, and that app was rejected by Apple, then allowed back in for sale, but without access to the 3G network. It's pretty clear that FCC Chairman Julius Genachowski thinks there is more to be done to get consumers the best deal, and he's putting the cellular carriers on notice that they will be closely looked at. Readers: Are you happy with cellular service as it stands today? Do our friends in Europe get a better deal?
FCC formally launches inquiry into wireless competition
Well, we can't say we didn't see this one coming. At today's meeting, the FCC has said that it will be launching a formal inquiry into the wireless industry and specifically into certain business practices of the big four: AT&T, Sprint, T-Mobile USA , and Verizon Wireless. The commission hasn't yet detailed exactly how they're going to go about this, but you can bet they'll be looking into exclusivity deals between handset manufacturers and carriers. And who knows? They might be interested in the whole iPhone / AT&T / Google Voice conundrum, especially if it turns out that AT&T had a hand in dissing the app. According to Reuters, the agency is looking into "how competition affects consumers," with an eye towards further investigations into other areas, including cable and broadband. [Via Phone Scoop]
Editorial: Apple, the FCC, and the sideloading solution
As Engadget's resident former attorney, my first instinct when I sat down to re-read Apple, AT&T's and Google's FCC filings regarding Google Voice was to put on my lawyer hat and try to find inconsistencies that might shed some additional light on what had actually happened -- if Apple's account differed from AT&T's, for example, perhaps those subtle differences would reveal the actual truth. This proved to be much more difficult than I had imagined, however: not only had Google redacted the most interesting part of its statement, I came to a profound realization after just a few moments of work. I don't care. Each of the responses was long, dense, and polished to a high-gloss shine that made each company's actions seem not only rational and justified, but almost inevitable in a way -- as I wrote at the time, Apple isn't exaggerating when it says that these are entirely new problems, and simply reading the individual letters paints a fairly sympathetic picture of how this whole chaotic process ended up in such disarray. But that's a perspective that assumes deeply-rooted interest in the systems and procedure of the App Store, a perspective that assumes there's a good reason we should be looking to lawyers and government regulators to figure out what's going on with the most exciting and vital software market that we've seen in a long time.
