The document discusses the limitations of responsive design alone in optimizing web experiences across various devices and browsers. It highlights issues such as legacy browser support and the challenges of managing large content effectively. Several tools and frameworks are mentioned to enhance responsive design, emphasizing the need for developers to adopt a broader approach beyond mere responsiveness.

1. Why Responsive Design
isn't enough
(by itself)

2. Nathaniel Schweinberg
@nathanielks

3. What Problems are we trying to
solve?
Serving optimized experiences across devices/browsers
Having only 1 website
Maintaining 1 codebase

4. A Good Start
@media queries are great!

5. What issues are we facing?
Legacy Browsers
Content Delivery
Who gets What and How

6. The Underlying issue?

7. Websites got Big Asses

8. Images!

9. Request Headers!

10. Why "Responsive Design"
isn't enough

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

12. What is Responsive Design?

13. Responsive sites are made up a
few things
Good Content
Design
Development
Maintenance/Testing

14. Content Creation
Keep things simple

16. 320 & Up
Base css is simplified mobile, customise for IE
All major browsers support @media

17. Image Handling
Adaptive Images
No end all solution yet

19. Content Delivery
Media Queries
Adapt/Responsive.js
Mustache

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

21. Optimized Scripts
Mobble
WURFL

22. Be Responsible Developers, not
responsive developers

23. Client Side Resources
Adapt.js Ruby gems:
Respond.js SASS
Retina.js Susy
LESS Bourbon
Bootstrap Neat
Foundation
A bajillion other frameworks Codekit

24. Server Side Resources
Mustache
Adaptive Images
WURFL
Mobble
WP Fluid Images
WP Retina 2x

25. Real World Scenarios

26. Theatre Francais

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

29. Nathaniel Schweinberg
@nathanielks