Shared publicly  - 
Building Websites for the Multi-Screen Consumer.

This is truly a useful whitepaper from my colleagues at Google. Read it:
Ralf Bachmann's profile photoBryson Meunier's profile photoAmmon Johns's profile photo
Unfortunately this white paper has a disadvantage light grey text is very difficult to read on white background ;) 
Not enough cons in the responsive web design section but a good whitepaper nonetheless. I'm surprised they didn't at least mention that responsive design is not recommended by Google for feature phone users, given that they say "Remember also that for an increasing number of people, mobile is the only screen. This is especially true in emerging markets and with younger people everywhere." Not a small omission. You know, +Pierre Far that as much as I like you I will continue to point out glaring errors like this and the ones from your team's video on responsive design as I did recently on Marketing Land: I hope that one day Google will make this unnecessary by publishing the full story on all three mobile site configurations but I'm not holding my breath.
Its a great start, with some good points.  I'd have liked to see a little more emphasis on the figures and needs for multi-screen.  I know it was there, but it was very minimal.  Many businesses that own websites don't 'live' online to the extent that SEOs (and Google staff) do.  It takes longer, and more evidence, for them to truly get it.

I also think a lot of the information from Google lately has been overly positive about responsive design.  The truth in the real world is that the majority of sites, certainly ecommerce sites and wordpress sites, are generally massively over-bloated with scripts and CSS that offer very little value to the genuine mobile customer. 

Responsive design typically merely styles and sizes the same content for all in most cases, forcing mobile users, (who usually pay for data transfer, and have the least screen real estate to enjoy effects) to download scripts and assets that make little or no difference to them, and slow the mobile experience compared to a dedicated, stripped-down mobile experience designed for speed and utility.

Whilst the paper does mention this in the section about a strength for dynamic serving, it should also mention this clearly as a common weakness in responsive design.  At a time when Google, (and you personally) have been stating over and over how important speed is for a mobile experience, its a major ommission not to include that vital aspect in the white paper.
Add a comment...