Measuring the Effects of Operator Transcoders

The issue of mobile-operator transcoders on the mobile web has been hugely controversial. For many iPhone and Android phone owners the negative effects of the transcoders are no longer visible and the issue has dropped off the radar, but they remain a serious problem for those using lower-end devices.

The potential benefits of transcoders are clear: they can make some desktop-oriented web content work acceptably well on mobile devices. But the cost of this can be very large: many mobile operators are still utilizing transcoders that have disastrous effects on made-for-mobile content, without offering content owners any way to bypass them. This reduces usability and hampers the growth of the mobile web by disincentivizing the content creators.

We have now heard so much about this issue that we are considering taking further action.

Our approach will be a project to document the impact of operator transcoders around the world. We will build a set of test sites and pages, partially based on the W3C CTG tests, that will enable people to test what the transcoding engines are doing in different test scenarios. This will documented in a series of steps that should be performed. This is a very complex area since it depends on many variables:

  • the browser in question
  • the device in question
  • the page content and URI of the page under test
  • the APN in use by the device

To produce meaningful results all of the factors mentioned above will need to be documented for each result, since the tests are meaningless otherwise. It seems likely that, at most, the results of any test will say something like: For device X, provisioned with configuration Y, and APN Z, certain tests failed.

Human testing will be necessary because many of the searched-for effects are not programmatically discernible.

By necessity, this will need to be a community project, since we will need volunteers around the world to test their local operators. If we receive sufficient interest from the community we will proceed with this project in an open way. The intention is to use mobiForge as a central point where the effects of operator transcoders are documented. Our hope is that by raising awareness of the effects of transcoding and detailing who exactly is doing it badly, we can effect some changes.

Please let us know via comments or email if you think that this is a project worth pursuing, and if you would like to contribute via a forum to flesh out ideas.

Exclusive tips, how-tos, news and comment

Receive monthly updates on the world of mobile dev.

Other Products

Market leading device intelligence for the web, app and MNO ecosystems
DeviceAtlas - Device Intelligence

Real-time identification of fraudulent and misrepresented traffic
DeviceAssure - Device Verification

A free tool for developers, designers and marketers to test website performance
mobiReady - Evaluate your websites’ mobile readiness

© 2024 DeviceAtlas Limited. All rights reserved.

This is a website of DeviceAtlas Limited, a private company limited by shares, incorporated and registered in the Republic of Ireland with registered number 398040 and registered office at 6th Floor, 2 Grand Canal Square, Dublin 2, Ireland