Transcoding web pages into mobile web pages does not work.

There’s an ongoing debate on the subject of mobile web transcoding, so here’s our take.

Let’s be clear on our language here though. Transcoding videos for mobiles is essential and very good, but doing it to your web output is bad. Really bad.

A reliance on an automated process that takes HTML output and reformats it to mobile markup is a deluded one. Computers are really bad at recognising diverse visual patterns (that’s why we all use CAPTCHA to protect from bots) and you don’t get much more diverse than web design. If a transcoder has been taught your web layout, you’ll find yourself tied to that web design or face losing any learning invested in the system.

The core point however is that mobile users have different desires and demands to you normal web audience. They don’t want to search for information – they want it served to them. They want access to services that are typically mobile, not those that are more comfortably engaged in while sat in front of a 19inch monitor with time to spare.

The solution is to write mobile applications for mobile from the heart of your server outwards, sharing logic and data.

With this approach you can utilise all the logic, models and controllers (if you’re that way inclined) from your existing web services but present them using view layers that are ideally suited to mobile devices. You can omit features that are simply not made for mobile and include new ones that would mean nothing to a web audience but are essential to visitors on the move.

Wapple Architect allows you to output a single markup language for every mobile device. The process will automatically adapt your WAPL markup to each and every mobile device – but this isn’t transcoding – it’s taking the output, layout and data described in WAPL and returning the correct markup for any particular device.  Watch this video to understand more.

Wapple Architect beats automated transcoding

Don’t be fooled by the sirens singing the song of transcoding. They will bite you in the backside sooner or later. Transcoding is at best a quick fix but as an enterprise level approach to catching the mobile web wave it will ultimately disappoint your users, create an extra layer of work for you over and over and simply glosses over an issue rather than addressing it entirely.

Code, don’t transcode.