The mobile web is still only a fragment of the wider desktop web we use everyday, so one of the challenges operators, website owners and users face is how on Earth to cram this big web onto small screens.

Different people tackle the problem in different ways, as the Sender 11 blog points out:

Apple: Adapt the phone to the web.
Opera: Adapt the web to the phone.

But then, there’s a third option: Bulldoze everything with a transcoder, including sites which are already mobile, and don’t shed a tear for the casualties.

This approach has unfortunately been adopted by a number of operators, namely Vodafone and TeliaSonera with Novarra, and Sprint with OpenWave.

When I think of the carelessness these guys are exhibiting, I get a Hulk moment “Vero angry, Vero smash phones! ARGGHHHH!” It boggles the mind how Sprint can go as far as saying it’s in the customer’s best interest. If they really cared about the customer experience, they wouldn’t highjack user agents, they would acknowledge sites which are already mobile-ready and they would listen to the community’s needs.

Anyone who isn’t directly involved in the mobile industry is unlikely to realise that the site they’re browsing looks crap on their phone, not by the website owner’s fault or because their phone isn’t up to par, but squarely because of the operator’s complete disregard for its customers. A little bit of me dies every time I see a friend criticize the mobile web’s shortcomings when it’s really due to bastardised transcoding.

Operators claim to be offering a proverbial olive branch by telling mobile website owners to request to be added to a whitelist. Dennis at Wapreview sounded the alarm on the latest whitelist to join but this is a neverending game of whack-a-mole! As far as I know, between Spain and the UK, Vodafone doesn’t even share its whitelist! (If anyone can tell me I’m wrong on this one, I’ll regain a bit of faith in the Big Red.)

As Dennis explains, unless you have a handset on the local network, it’s difficult to find out what’s happening to your site once it goes through the shredder:

Unless you have a Sprint handset there’s really no way to tell if your site’s being transcoded. If you do have a Sprint phone you can generally tell just by looking at the screen but if in doubt use the device’s Show URL browser menu command. If it starts with http://sprint.aopwv.com/ you are being transcoded.

Mobhappy, Mike Rowehl, Techype, RCR Wireless News and Semapedia, amongst others, have picked up on the issue, and they’re all as unimpressed as I am with the situation.

How could anyone, in their infinite wisdom, think this was a scaleable and manageable way to decide what sites to leave as-is? Seriously, I’m willing to give anyone from an operator a fair hearing, I’ll even buy ‘em a beer, if they can explain to me how they’re going to improve on the current situation from here.

If you’re a developer and your mobile site is affected by the latest Sprint issue, register on the Sprint forums and leave a comment in this thread to get whitelisted.

[Update: Russ at Mowser posted, following my angry post, to shed light on how what Mowser does is different to the operator’s transcoders, so if you’re still fuzzy on what is proper and improper behaviour for adapting content, check out his post. At the core of it all though, Mowser listen to their users and are part of the community rather than living up in that cozy ivory tower. That makes all the difference.]

This entry was posted on Thursday, March 20th, 2008 at 11:38 am and is filed under Network Operators. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.