- dotMobi Compliance - Posted by ronan 5 years 11 weeks ago
dotMobi Mobile Web Developer's Guide- I am proud to announce we recently posted the dotMobi Mobile Web Developer's Guide on mobiForge. This is quite a comprehensive guide to mobile web development. It layers on the advice from the W3C's Mobile Web Initiative Mobile Web Best Practices 1.0 document, but takes it further.
- dotMobi Compliance - Posted by ruadhan 3 years 1 week ago
Mobile Web Benchmarks: What can you do?- Yesterday, Gomez and dotMobi published a second set of mobile Web benchmarks. The metrics are taken across three key industries: banking, airlines, and search, each of which represents an exciting and important slice of the mobile Web. I don't want to analyse the results here (the mobile Web is getting slower apparently!) - instead, I'll take a brief look at what these benchmarks might mean for you as a developer.
- dotMobi Compliance - Posted by ruadhan 3 years 48 weeks ago
Ready.mobi v2.1.1 is live- You can probably guess by the version number 2.1.1 (from 2.1), there is nothing ground-breaking in this release. Just a few more bug fixes. In particular we have fixed a bug that caused the use of multiple <hr/> tags in your markup to reduce your overall score.
- dotMobi Compliance - Posted by ruadhan 4 years 15 weeks ago
Fixit - Image Resizing- Images such as bitmaps have an intrinsic pixel size. Telling the browser in advance what the size is avoids it having to re-flow the page when it receives it. Resizing images at the server reduces the amount of data transferred and the amount of processing the client has to carry out to scale the image.
- dotMobi Compliance - Posted by ronan 4 years 15 weeks ago
Making your .mobi domain compliant- The .mobi domain is unlike all other domains in that it has a set of rules that web site owners must follow -- most other domains such as .com, .net, and .org do not have any technical requirements about the content hosted in the domain. The .mobi rules often cause confusion amongst site developers and domain holders so we thought we'd try to help people get their domains to pass muster.
- dotMobi Compliance - Posted by ruadhan 4 years 15 weeks ago
Fixit - Measures- Avoiding pixel and absolute measures allows the browser to adapt content to fit the display, though there are exceptions to this rule (see below). This test checks for the use of absolulte and pixel measures where relative measures would be more appropriate
- dotMobi Compliance - Posted by ruadhan 4 years 16 weeks ago
Fixit - Tables- This test determines if your page uses tables. Tables do not work well on limited size screens and may result in the user having to scroll horizontally to read them. Putting navigational links into tables may result in the user having both to scroll horizontally and vertically to see possible navigational choices.
- dotMobi Compliance - Posted by ruadhan 4 years 16 weeks ago
Fixit - Tables for layout- This test attempts to determines if your page is using tables for layout purposes. Tables should be used to present tabular data, rather than to control the layout of a page. The problems associated with using tables for layout are well documented. In particular, they generally require more markup and take longer to render than acheiving the same with CSS.
- dotMobi Compliance - Posted by ruadhan 4 years 17 weeks ago
Fixit - Nested Tables- This test determines if your page make use of nested tables. Mobile devices often cannot display nested tables correctly. When a mobile device is capable of displaying nested tables, the computations required to render the tables can consume lot of CPU and add to the display time for the page.
- dotMobi Compliance - Posted by ruadhan 4 years 17 weeks ago
Fixit - External Resources- This test determines how many externally linked resources your page relies on. Linked resources include images, stylesheets and other objects. Each externally linked resource requires a separate request across the network. This may add a significant amount to the page load time in the mobile context.


