Why Responsive Design isn't enough

(by itself)

Nathaniel Schweinberg@nathanielks

What Problems are we trying to solve?

Serving optimized experiences across devices/browsersHaving only 1 website

Maintaining 1 codebase

@media queries are great!

A Good Start

Legacy BrowsersContent Delivery

Who gets What and How

What issues are we facing?

The Underlying issue?

Websites got Big Asses

Images!

Request Headers!

Why "Responsive Design"isn't enough

http://mpulp.mobi/2011/05/next-steps-of-responsive-web-design/

What is Responsive Design?

Good ContentDesign

DevelopmentMaintenance/Testing

Responsive sites are made up a few things

Keep things simple

Content Creation

320 & Up

Base css is simplified mobile, customise for IEAll major browsers support @media

Adaptive ImagesNo end all solution yet

Image Handling

Media QueriesAdapt/Responsive.js

Mustache

Content Delivery

http://www.lukew.com/ff/entry.asp?1392

MobbleWURFL

Optimized Scripts

Be Responsible Developers, not responsive developers

Adapt.jsRespond.jsRetina.jsLESSBootstrapFoundationA bajillion other frameworks

Client Side ResourcesRuby gems:

SASSSusy

BourbonNeat

Codekit

MustacheAdaptive ImagesWURFLMobbleWP Fluid ImagesWP Retina 2x

Server Side Resources

Real World Scenarios

Theatre Francais

https://kippt.com/nathanielks/responsive-resources

Resources:

Nathaniel Schweinberg@nathanielks