Tag: google voice (Page 1 of 2)

Official Google Voice app might already be approved

Google Voice logo.It’s been more than a year since Apple pulled the original Google Voice app from the App Store, claiming that the product “duplicated existing functionality.” Some third-party GV apps have since made their way to the App Store, thanks in part to Apple’s decision to release app guidelines to the public. If TechCrunch is right, it sounds like the official Google Voice app may already be approved, marking the triumphant return of one of the most anticipated applications to the iPhone.

Here’s what TC had to say:

The App Store review office at 1 Infinite Loop has officially frozen over: we’ve gotten word that the official Google Voice application is on its way to the iPhone in the next few weeks. In fact, we’ve heard from a source close to Google that it’s already been approved — Google just needs to revamp the application to work with the iPhone 4 and iOS’s multitasking capabilities. If you’re a Google Voice user and you’re on an iPhone, this is great news.

No word from Google, but I’m hoping it’s only a matter of time.

Google Voice returns to the iPhone

GV Connect.It’s been more than a year since Apple pulled Google Voice off the iPhone, but there’s finally reason to celebrate for Google Voice fans. Apple has approved at least one native app for the iPhone.

What does that mean? That means no more jailbreaking, no more hacks, no more ridiculous excuses from Apple about feature duplication and whatnot. It means you can use GV Connect – the app that was approved – to make calls, transcribe voicemails, send SMS messages, record conversations, star conversations, and notes to conversations and messages, and basically provide everything you want from Google Voice right on your phone.

All I can say is it’s about damn time. This is a solid year overdue. I almost understood Apple’s reasoning, especially when Google Voice was sort of new and confusing. A couple months after the initial rejection, though, and this thing should have been back in without question. Really, it probably never should have been pulled, but this wait has been long.

Droid isn’t just for Verizon

Droids for AT&T.The most recent info on Motorola’s Droid suggests that the phone isn’t just for Verizon. In fact, it looks like there’s a GSM model that would work on AT&T’s 3G network, as well as Canada’s Rogers.

So it looks like the new name for the “Droid” is now “Sholes,” at least pre-release. That’s the name buried deep in the FCC docs that also show the AT&T 3G bandwidths. To me the big advantage of the phone would be that it’s a nice piece of hardware for anything other than AT&T. If I was going with AT&T, I think I’d still stick to the iPhone. Android still has some catching up to do in the app department for me to genuinely consider a switch. Although there is that Google Voice thing…

FCC looking at Google Voice

Google Voice logo.The FCC is going to be taking a closer look at the Google Voice service to determine whether it should be governed by the same rules as other phone service operators. AT&T has been particularly whiney about the service and the lack of regulation.

The biggest problem AT&T sees is that Google is allowed to block calls that may be too expensive for users, something regular providers aren’t allowed to do. I’m not sure why AT&T has such a problem. It blocks calls all the time. You know, you get halfway into a call and AT&T decides it should be blocked. And you should not be compensated for any lost time. It also blocks your ability to have a truly unlimited data plan and blocks your phone from having basic services despite years of availability on other devices. Really, AT&T is blocking anything it wants, so why not spread the love?

I do find it funny that it took a high-profile app rejection to bring all of this to light. The results of the investigation will likely be applied to other VoIP services like Skype and Vonage, both of which have been around a whole lot longer than Google Voice. The unfortunate thing is that big wireless could gouge features out of customer-focused service because it fears competition.

The FCC needs to stop coddling big wireless

Julius Genachowski.FCC Chairman Julius Genachowski sounds pretty pleased with steps wireless providers have taken over the past week. In a speech today he complimented AT&T for its recent 3G over VoIP commitment and Verizon and Google for upcoming Android headsets that will support Google Voice. The speech was among the most pejorative things I’ve read (get the full text here), and I couldn’t help feeling insulted at all the back-clapping going on.

We’re still a long way from a level of consumer respect that I find acceptable, so comments like the following rub me raw:

That’s because all of you are changing the world. You’ve turned clunky one-trick handsets into sleek and powerful mini-PCs. You’ve made the Internet mobile, freeing broadband from the desktop and making it possible to imagine a world where the Internet is available to anyone, anywhere, anytime.

You’re making that possible through the billions you’ve invested, and the billions you plan to invest.

I’m sorry, I guess I didn’t realize how nice the wireless companies have been. It’s almost like they aren’t making billions back through ridiculous airtime and data charges, egregious texting plans, and obscene service outages and dropped call rates. Granted, I don’t line nearly as many pockets in Washington as these companies do, but Genachowski addresses them like spoiled children. “Great job, Timmy. You only punched three girls today, not four, and frankly, two of them deserved it.”

I’m all for government support of broadband expansion and commitments to improved service, but let’s not coddle big wireless. Sure AT&T opened up to VoIP, but it took an FCC investigation to get it there. I pulled crap like this on my parents all the time. Sure, I was nice to my siblings, but as soon as I was alone I was scribbling swear words on the bathroom wall in red Sharpie.

Source: Reuters

« Older posts

© 2026 Gadget Teaser

Theme by Anders NorenUp ↑