Re: MobileOK scheme

Charles McCathieNevile wrote:
> On Mon, 15 Jun 2009 20:18:10 +0200, Jo Rabin <jrabin@mtld.mobi> wrote:
> 
>>> It seems to be an improvement, but I specifically object to that things
>>> which provide an enhanced experience for better browsers are not
>>> mobileOK, or even are likely not to be MobileOK.
> 
>> If you provide a response that is wider than 120px in response to a 
>> User Agent of DDR that is not mobileOK. If you provide the same 
>> response when the User Agent is not the DDR then it's neither mobileOK 
>> nor not mobileOK.
> 
> Right. Which is different from "it is not mobileOK".
> 
>> I don't understand your objection which seems to be rather to do with 
>> mobileOK Basic Tests than this document.
> 
> No, it is with the specific phrasing that says "doing a really good job 
> is not mobileOK", rather than saying "doing a good job can also be 
> mobileOK and is encouraged in the overall work behind mobileOK".

And I thought Groundhog day was in February.

I don't think there's a lot of disagreement here. The spirit of 
mobileOK, and, AIUI, the letter of it, is that you must be able to 
return a basic representation in the absence of information that says 
you're talking to a more able device. Users of devices that are more 
capable device have a reasonable expectation that they will get a 
representation that exploits their device's capabilities to present 
something better.

In other words, being mobileOK means that you can deal with simple 
devices> Since there is no agreement what a more capable device can do, 
we can't say that mobileOK means that you can also do X, Y and Z. 
However, an Opera Mini user, or an iPhone user, can be reasonably sure 
that a mobileOK site will exploit the capabilities of their device in 
such a way as to give them an enhanced experience.

Again, mobileOK and the BPs from which it is ultimately derived do not 
mean working to the lowest common denominator.


Dunno if that helps any.

Phil.

Received on Monday, 15 June 2009 22:08:36 UTC