{"id":386,"date":"2007-08-29T22:41:04","date_gmt":"2007-08-30T05:41:04","guid":{"rendered":"http:\/\/wapreview.com\/?p=386"},"modified":"2020-09-27T20:35:57","modified_gmt":"2020-09-28T03:35:57","slug":"readymobi-great-resource-for-mobile-web-developers","status":"publish","type":"post","link":"https:\/\/wapreview.com\/386\/","title":{"rendered":"Ready.mobi – Great Resource for Mobile Web Developers"},"content":{"rendered":"

Dev.mobi has updated their free Ready.mobi<\/a> site checker. The checker’s developer Ruadhan O’Donoghue, has a nice writeup explaining the new features here<\/a>. I’m very impressed with this new mobile web development tool.<\/p>\n

There are really two separate ready.mobi checkers. The basic checker, which requires no registration, checks a single page on 32 points of compliance with mobile web best practices. There is a mobile device emulator built into the result page that lets you see the site as it would appear on 5 different handsets. The emulator is a a licensed commercial product from Yospace<\/a> which you get to use for free. The full blown, and admittedly much more feature rich, Yospace developer edition is \u00a3299 ($600) so this is a pretty good deal.<\/p>\n

\"Ready.mobi<\/p>\n

If you register on the dev mobi site, which is also free, you can use an advanced crawler which recursively checks every page of one or several sites. The recursive checker is nothing short of amazing. It plows through an entire site in a couple of minutes and comes up with these great reports that you can drill down into on a page by page basis to see exactly what problems were found.<\/p>\n

\"Ready.mobi<\/p>\n

These are both fantastic tools for the mobile web developer. There’s really nothing else like them. Besides testing markup, page size and adherence to the mobile ready guidelines you also get to see your site on five different emulated handsets. It’s not perfect, the test for “default entry mode” is broken in that it doesn’t recognize the valid xhtml-mp syntax for specifying input mode. I don’t completely agree with some of the best practices either but there’s no faster way to find the odd page on your sites that is too large or has validation errors. I thought my sites were pretty clean but ready.mobi found a problem. One of my pages was missing it’s DTD and had some invalid markup too.<\/p>\n

I really have to hand it to the .mobi group<\/a>. I had some reservations about the need for a separate mobile domain when it was announced. I wasn’t crazy about the choice of the hard to type .mobi over say .m or even .wap. I didn’t see any reason why a .mobi domain should cost $20\/year when I could get .com or .net one for $6. But .mobi has really redeemed itself by giving back to the community of mobile publishers and developers. Much of that $14\/year is going to .mobi’s constant marketing of the mobile web, their support of the WURFL<\/a> project and especially their great dev.mobi<\/a> developers site which is loaded with tutorials, sample code, page templates and some pretty active developer forums. Dev.mobi is more useful overall than any of the handset manufacturer and carrier’s developer sites.<\/p>\n","protected":false},"excerpt":{"rendered":"

Dev.mobi has updated their free Ready.mobi site checker. The checker’s developer Ruadhan O’Donoghue, has a nice writeup explaining the new features here. I’m very impressed with this new mobile web development tool. There are really two separate ready.mobi checkers. The basic checker, which requires no registration, checks a single page on 32 points of compliance with mobile web best practices. There is a mobile device emulator built into the result page that lets you see the site as it would … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":21775,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[51],"tags":[],"_links":{"self":[{"href":"https:\/\/wapreview.com\/wp-json\/wp\/v2\/posts\/386"}],"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=386"}],"version-history":[{"count":1,"href":"https:\/\/wapreview.com\/wp-json\/wp\/v2\/posts\/386\/revisions"}],"predecessor-version":[{"id":21774,"href":"https:\/\/wapreview.com\/wp-json\/wp\/v2\/posts\/386\/revisions\/21774"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/wapreview.com\/wp-json\/wp\/v2\/media\/21775"}],"wp:attachment":[{"href":"https:\/\/wapreview.com\/wp-json\/wp\/v2\/media?parent=386"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/wapreview.com\/wp-json\/wp\/v2\/categories?post=386"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/wapreview.com\/wp-json\/wp\/v2\/tags?post=386"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}