Mobile friendly isn't a meme, it's just a description of how well your chosen presentation of content translates into a different context of use. Context changes often require different choices about how you break up your content to throw at someone - this has been the case since the web began.
Shifting the layout burden to content supplied (and or javascript) was/is a huge mistake, the browser on the device should do the layout using whatever style hints it feels are appropriate.
Works well, looks identical on all devices, is future proof: pick any two.
Pointer-driven UI and touchscreen UI have different local maxima. One of the reasons Ubuntu's Unity looks like it does is because they intend for it to look and work well on both UI types.
(OTOH, the up/down buttons on HN are not desktop friendly either)
Perhaps an alternative would be some declaration that says "Hey render me this way if you feel like it, but use these all powerful browser supplied styles if I become unreadable"
Some browser's have implemented that reading mode (safari?) and it seems like a cool idea, but I think it only works if you provide really good HTML5 markup.
if it were a display protocol then we could have kept things a lot simpler, specify display width, height and DPI in the request, get back a compressed image and a bunch of 'hot zones' or 'fields' in response. Such protocols existed and they did not make the cut, the one that did explicitly left the rendering decisions to the client receiving the data.
Websites are not pixel perfect renditions created by dictates issued from servers, they are streams of information decorated with meta-data that give hints on how the information could be rendered.
http://en.wikipedia.org/wiki/Hypertext
> A browser can not predict the particulars of my design well enough to make those decisions for me.
On the contrary, you are not capable of predicting the context in which the information you supply will be used, so less design is better. If you want pixel perfect eye candy write an application but don't use the web, it's lossy by design, for all you know your information will be presented in an audible rather than a readable form, will be printed out on a printer that does not support colour and/or will be read with a device 10,000 years into the future.
Your design is not relevant, the information is what is relevant.
Note that in the case of content such as 'flash', 'silverlight' and other plug-in related content this is going to be a major problem.
Finally, in the interest of commerce and user experience website owners are free to improve their sites to enhance the experience for their users but they should not be required to get basic functionality working.
The "let the browser decide" ship has sailed, and the designers won (with our support, I might add). All we can do now is use those a same tools to take back control.
Mobile browsers should offer a custom style option, or at least a "no style" option like FF does.
Sidenote: Is it possible at all to have horizontal scrolling websites that Google consideres mobile friendly? Some websites are intended to have a horizontal scroll. What are they supposed to do?
The pixel-perfect coupling that people expect between what a site should look like according to the designers and how that site is rendered by the browsers is an illusion, that's not the way the web was supposed to work at all, web sites provide information and loose markup hints and browsers then render that information in the best way suitable for the device and its user.
Don't blame the website, blame the browser instead.
Ironically, looking at ancient (pre-CSS, pre table based layouts) websites through modern browsers gives you instant adaptive design because all there was was content, no eye candy.
If we had wanted pixel based rendering we could have done a damn sight better than CSS, style sheets and markup are hints, not ultimatums to be obeyed or failure will occur.
Just think about the burden that these demands make on older websites, websites that worked perfectly well in the past suddenly need to be modified in order to be displayed properly, that's a total inversion of the way things are supposed to work. Old content and older websites should be displayed with as high fidelity as possible on newer browsers and devices. You can't fault the makers of old websites for not being 'future compatible' but you can fault the makers of new devices and browsers for not being compatible with the past.