Chitika

Don't blame AT&T for the 3G iPad's video streaming failings

Wednesday, May 26, 2010



Customers began receiving their 3G iPads on Friday, as expected. The hardware was purportedly the same as a wi-fi only iPad. You might expect, with the exceptions for applications we know don't work on 3G on the iPhone (like Skype), that everything should work the same, 3G vs. wi-fi. You'd be wrong, but honestly, should you have expected any less?

Based on experiences with the iPhone and 3G vs. wi-fi on applications, there were certainly suspicions that quite a few things might not work on the iPad. For example, the "ABC Player for iPad" won't work on 3G. Instead, users receive the message, “Please connect to a Wi-Fi network to use this application. Cellular networks are not supported at this time.”

Additionally, the iPad's built-in YouTube application "strips both standard and HD videos to a dramatically lower resolution over the cellular data connection." Meanwhile, it appears that iTunes Store video previews are just fine (wonder why that is? ... insert sarcasm here).

Netflix, however, appears to be working normally. The question is, why the differences between applications?

This is the same sort of thing that's still happening on the iPhone, where Skype still has no 3G capable application, but Fring does. Once again, why the difference?

While the first finger to be pointed would obviously be targeted right at AT&T, whose 3G network has struggled under the weight of the iPhone, much less the iPad (AT&T supplies the 3G service for the iPad in the U.S.), an AT&T spokesperson replied: "It’s just a question for Apple."

Hmm. Finger pointing from AT&T toward Apple. Meanwhile, Business Week's Dan Frommer tweeted:

ABC is wifi only on purpose. I believe rights play a role. (they're different on wifi vs 3G) sounds dumb but true.

Bottom line: AT&T is a popular whipping boy in issues like this, and we would be remiss if we did not point out that indeed, their 3G network leaves a lot to be desired, but the answer here is fragmented and probably specific to each "failed" app.

Labels:

0 comments: