{"id":9096,"date":"2011-01-25T12:28:28","date_gmt":"2011-01-25T20:28:28","guid":{"rendered":"http:\/\/blog.wapreview.com\/?p=9096"},"modified":"2011-01-25T16:58:11","modified_gmt":"2011-01-26T00:58:11","slug":"dont-let-thematic-inconsistency-bite-your-mobile-users","status":"publish","type":"post","link":"https:\/\/wapreview.com\/9096\/","title":{"rendered":"Don’t Let Thematic Inconsistency Bite Your Mobile Users"},"content":{"rendered":"
<\/p>\n
I do most of my casual web surfing on my phone. The PC is primarily for work; writing code and prose,\u00a0 editing images, etc. The phone is where I catch up with the news and skip from link to link exploring new topics, sites and authors.<\/p>\n
Usually my mobile surfing starts with a link in Twitter or Google reader. Most of the time it works. But about once a week I click on a link to a story and it takes me to an error page or a news site or blog’s mobile home page with the article I wanted to read nowhere to be found.<\/p>\n
It happened again today. I clicked a short link on Twitter to read what I though was going to be an op-ed piece on the tragic Moscow airport bombing<\/a> and got a ‘file not found error’. It turned out that the short link was to a recent item on Salon.com.\u00a0 The link worked perfectly in my PC browser but when I tried to follow the same link on my mobile, the site’s browser detection redirected me to an “m.” version of the same story, which doesn’t exist for some reason.<\/p>\n I played around with Salon’s mobile and desktop sites and found a couple more deep links that gave errors in my mobile browser, although the vast majority worked fine. I’ll rack this one up to random bug somewhere in Salon’s infrastructure that breaks the odd page now and then.<\/p>\n Links, including deep links, are the glue of the Internet. With more and more browsing occurring on mobile devices it’s important for publishers and designers to make sure that a link or bookmark from one device works on all devices.<\/p>\n The W3C calls this principle “Thematic Consistency” which they define as<\/a>: “Thematic consistency does not mean that the content has to match exactly. It means that, as far as is reasonable:<\/p>\n In short, it means that users who switch from one device to another should not have to wonder: “Where is this piece of information I’m looking for? I know it’s there, I saw it on my laptop!” A single glance at the different versions should be enough to say “OK, that’s the same thing”.<\/p><\/blockquote>\n I don’t always agree with the W3C but they got this one right. Don’t redirect a request for a specific page to the mobile home page or a nag page telling the user to visit the site with their PC. If the resource isn’t available in a mobile formatted version, serve the mobile user the desktop page, most modern browsers can handle just about any page. An increasing number can even deal with Flash.<\/p>\n","protected":false},"excerpt":{"rendered":" I do most of my casual web surfing on my phone. The PC is primarily for work; writing code and prose,\u00a0 editing images, etc. The phone is where I catch up with the news and skip from link to link exploring new topics, sites and authors. Usually my mobile surfing starts with a link in Twitter or Google reader. Most of the time it works. But about once a week I click on a link to a story and it … Continue reading
\n\ufeff\ufeff<\/p>\n\n