Update:<\/strong> Creative-Weblogging has fixed most of the browser detection issues with their mobile sites making much of what I wrote below no longer true. Opera Mini and Netfront are now recognized as mobile devices. See <\/em>Creative-Weblogging CEO Torsten’s comments. It sounds like he is committed to making the CW sites mobile friendly. If you have a mobile browser that’s not getting the mobile edition of one of the Creative-Weblogging sites please leave a comment and I’ll try to pass it on. – Dennis 22-Jan-2007<\/em><\/p>\n

Another enhancement, now you can force a mobile page to be rendered by adding index_xhtml.php to the end of any of the creative-weblogging urls, for example http:\/\/www.mobile-weblog.com\/index_xhtml.php<\/a>. – Dennis 24-Jan-2007 <\/em><\/p>\n

One of the blogs I find good enough to subscribe to is The Mobile Technology Weblog<\/a> (MTW). It’s a well written, lively mobile news and opinion blog covering what’s happening with mobile software, analysis of industry trends and pictures and specs of the most delicious new handsets.<\/p>\n

I usually try to read MTW on my PC because I’ve found it one of the hardest sites of any kind to read on a phone. BTW, this is not the fault of MTW’s bloggers, Tom Gordon and Scott Smith. MTW is part of a network of over 100 blogs called Creative-Weblogging<\/a> all of whose sites use the same basic page template.<\/p>\n

I’m using Opera Mini which is a “full web” browser that handles PC sites reasonably well, in fact the PC editions of most blogs are very usable in Opera Mini. But not this one. I have to scroll through 39 (I counted) screens containing the site’s linkroll, archive menu by month, a long list of categories, a calendar of events, a list of over 100 sister sites in the same blog network, a bunch of text ads, lists of recent comments and most popular posts until I finally reach the content! This is using a phone with a decent sized 176×220 screen that displays 17 lines averaging 22 characters per line. It’s much worse on an entry level phone’s 128×128 screen and not much better even with on QVGA screen. Of course, the site will render beautifully on the iPhone<\/em> :).<\/p>\n

The problem is the way the page’s html is laid out. Full-web browsers for mobile devices generally ignore CSS positioning and block element widths and re-flow the content as a single column in the order it occurs in the html document<\/strong>. The same is true of the screen readers used by the visually impaired and text-only PC browsers like Lynx. For a page to be usable by the largest possible audience it should be designed with document order in mind by placing the most important content near the top<\/strong>. The MTW site puts all the sidebar junk at the top of the markup with the content at the bottom and then uses CSS to move the main content block to the top left. This looks fine in modern PC browsers but nowhere else.<\/p>\n

The mobile web has arrived and Creative-Weblogging<\/em>, like blog-network rivals Gawker Media<\/em> (review of Gawker Media’s Lifehacker Mobile<\/a>) and Weblogs, Inc<\/em> (review<\/a>) and so many media and corporate sites of late, has rolled out mobile editions of all its blogs.<\/p>\n

The new mobile edition of MTW is quite nice, if you can actually get it on your phone, more about that later. It uses a mobile blog design pattern that I haven’t seen much of but which like a lot. The front page contains just the blog’s latest post followed by a link to the next oldest post and so on seemingly back indefinitely to the blog’s very first post ever. It’s a variation on the River of News<\/a> concept but one that works for mobile because by limiting pages to a single post, page size is kept below the 10KB limit of many low end mobile devices.<\/p>\n

I’m glad Creative-Weblogging is offering mobile versions of their blogs but there are a few problems with this version 0 of the mobile edition which I think could be easily remedied to make the experience even better. The biggest problem is that the mobile edition is only delivered when a mobile browser is detected and the browser detection doesn’t work very well. Both my phone’s built-in browsers are served the mobile version but all the full web mobile browsers like Opera Mini, Opera Mobile, Netfront 3.1 and 3.3 get the almost unusable PC version. The browser detection seems to be looking for the presence of “text\/vnd.wap.wml” in the browser’s HTTP_ACCEPT header to denote a mobile browser. As wml fades into the sunset, fewer and fewer browsers announce support for it.<\/p>\n

Another issue is that even supported browsers only get the mobile pages if they enter though the “front-door” – www.mobile-weblog.com.<\/a> Deep links to individual articles, like the continue<\/em> links in MTW’s partial feed go to the unusable PC version even when using a supported mobile browser. As a full feed isn’t offered, reading MTW in the mobile versions of Google Reader or Bloglines is painful as well.<\/p>\n

The Mobile Technology Weblog: Mobile Edition<\/a>: xhtml-mp
\nContent: Usability: <\/p>\n","protected":false},"excerpt":{"rendered":"

Update: Creative-Weblogging has fixed most of the browser detection issues with their mobile sites making much of what I wrote below no longer true. Opera Mini and Netfront are now recognized as mobile devices. See Creative-Weblogging CEO Torsten’s comments. It sounds like he is committed to making the CW sites mobile friendly. If you have a mobile browser that’s not getting the mobile edition of one of the Creative-Weblogging sites please leave a comment and I’ll try to pass it … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":21628,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[38,51,3],"tags":[],"_links":{"self":[{"href":"https:\/\/wapreview.com\/wp-json\/wp\/v2\/posts\/247"}],"collection":[{"href":"https:\/\/wapreview.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/wapreview.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/wapreview.com\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/wapreview.com\/wp-json\/wp\/v2\/comments?post=247"}],"version-history":[{"count":2,"href":"https:\/\/wapreview.com\/wp-json\/wp\/v2\/posts\/247\/revisions"}],"predecessor-version":[{"id":22906,"href":"https:\/\/wapreview.com\/wp-json\/wp\/v2\/posts\/247\/revisions\/22906"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/wapreview.com\/wp-json\/wp\/v2\/media\/21628"}],"wp:attachment":[{"href":"https:\/\/wapreview.com\/wp-json\/wp\/v2\/media?parent=247"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/wapreview.com\/wp-json\/wp\/v2\/categories?post=247"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/wapreview.com\/wp-json\/wp\/v2\/tags?post=247"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}