Parts 1, 2 and 3 of this 4 part post covered four mobile transcoding sites. Back in part 1, I defined mobile transcoding as “an application (usually a web service) which when given a request for any web page, does some sort of on-the-fly edit of the page to make it usable on the small screen of the a mobile device.” In this, the final installment, I look at one more transcoding engine, AOL and try to summarize what I’ve … Continue reading →

Revised 14-Oct-2006 to reflect improvements in both these transcoders. Skweezer has resolved it’s formatting and performance issues and now resizes images. Google has also added image resizing. I now consider these two transcoders esentially equal and the best currently available. Parts 1 and 2 of this 4 part post covered four mobile transcoding sites, WAP sites which reformat desktop web content to make it more usable on the small screen browsers of phones and PDAs. This entry looks at two … Continue reading →

Part 1 of this series of posts covered two mobile transcoding sites, loband and Phonifier. In part two we will look at two more, IYHY and MobileLeap. In case you missed Part 1, I define a mobile transcoding as “an application (usually a web service) which when given a request for any web page, does some sort of on-the-fly edit of the page to make it usable on the small screen of the a mobile device.” IYHY IYHY is another … Continue reading →

There’s been a lot of buzz lately about Mobile Transcoding which I define as an application (usually a web service) which when given a request for any web page, does some sort of on-the-fly edit of the page to make it usable on the small screen of the a mobile device. The promise of transcoding is that it will allow any web site to be viewed on any handheld device. I really don’t think a machine translation of a site … Continue reading →