Google did not axe Google Voice today. Sunday’s USA Today column didn’t say it would—it covered Google’s scheduled shutdown, effective today, of a protocol that other Internet-calling apps had used to connect to Google Voice—but many of you thought it did.
My first reaction on getting questions like “Is Google Voice being discontinued?” was to think “Gah! If that was really happening, don’t you think I would have said so right at the top of the story?”
My second: “Google, this is your own damn fault for neglecting the service for so long that people now expect the worst.”
My third reaction was a grudging acceptance that I should have foreseen readers skipping over my description of how Google Voice was shutting down the “XMPP” support that had allowed third-party VoIP clients to connect (admit it, you skimmed past that jargon just now) and instead seeing only the words “Google Voice” and “shutting down.”
That realization could have led me to write the column with fault-tolerance in mind: If there’s a way readers could get the wrong idea, throw in a “let me be clear” graf to disabuse them of that incorrect assumption. A little extra defensive writing then would have saved time since spent answering nervous reader e-mails and story comments.
I should know that by now, but apparently I’m still figuring out this writing thing after some 20 years of doing it for a living.
In other news: The Android Hangouts app still can’t place VoIP calls from your GV number (a capability the iOS version has had since October), officially leaving Android users in the lurch. Heck of a job, Google.
I led off this analysis of the latest Apple v. Samsung verdict by suggesting that the only sure winners were the children of the patent lawyers involved, who could now count on having their college tuition fully covered. A reader countered in a comment: “As the spouse of a former patent litigator, I take issue with the first paragraph. The children of these attorneys do not win in this scenario. The hours spent on this case are hours these parents will never get to spend with their kids. So pretty much everyone loses.” Fair point.
Google’s imminent end of support for a protocol that let third-party Internet-calling apps hook into its Google Voice service meant I had to explain why advice I’d offered a year ago in my USAT column is no longer operative.
It was another week that ended with a couple of stories filed but not yet posted (look for a long item on the Disruptive Competition Project in the next day or two about the state of competition in browser layout engines). But it’s not every week that sees me finishing it on the other side of the Atlantic–I’m spending the next four days in Barcelona to cover the Mobile World Congress show.
I took an unusually long time to try this activity-monitoring wristband–starting after CES. That leisurely pace allowed me to note the recent arrival of a similar background exercise-tracking option in Android’s Google Now app. Something like that won’t replace this wristband’s scrutiny of your sleep, but it could prove good enough for reporting whether you get off your duff often enough.
There are some other devices like this coming out over the next few months–the Fitbit Flex and Withings’ Smart Activity Tracker come to mind–so hopefully I can do a follow-up review of them.
My annoyance at having two Google Voice calls via Gmail leave the other person sitting there in puzzled silence led to this cheat-sheet guide to dialing out from your GV number. The column concludes with a tip based on a reader’s query on my Facebook page–yes, I really do read the comments there.