We’ve just gone live with an new version of the ready.mobi API. (Full details and code samples here). So what’s new in this version? The most notable feature in this version is the ability to post markup directly to the ready.mobi API without having to supply a publicly accessible URL to the service.
This is the result of some early feedback on the API that during the development cycle pages often did not have a public URL, and so they could not be tested with ready.mobi.
Of course, if you post markup directly to the service, this means that not all the Mobile Web Best Practices can be tested in full, since some of the tests rely on external factors such as HTTP headers and referenced resources. For instance, if you post markup directly to the ready.mobi API, we can tell you nothing about the size of the images that are referred to in your markup, and we can not determine if you are sending the correct HTTP headers (since we make no HTTP requests).
However, there are many useful tests that we can still perform. But because we don’t perform the ready.mobi tests in their entirety, we do not give a standard ready.mobi score between 1 and 5. Instead we just report a percentage taking into account the actual number of tests performed and passed.
For more information on how to get going with the API, check out this article which covers the basics and includes some sample code.
Leave a Reply