Keynote
summary
Claim: use responsive design for ~95% of cases, because media queries, fluid grids and client-side fixes handle layout and common tasks. Reserve dynamic serving or server-side adaptations when the server must send different content (NPR’s API example, CodePen and Beatport splitting players, Fidelity rearranging tables). Data cited: 91% of customers want access to content, 83% want seamless cross-device experiences. Adaptive approaches add complexity and maintenance and are justified only for narrow, measurable needs.
AI-written summary · about
chapters (11)
- 0:00Start
- 3:32Responsive Web Design
- 3:51Responsive Design
- 10:00Dynamic Serving
- 10:28Adaptive Design Is Server-Side
- 12:52Responsive Retrofit
- 22:58Targeting Information Based on Context
- 23:57Hearing Aids
- 25:57Scott Lee Ware
- 29:19Adaptive Design
- 29:52The Most Important Criteria for You When You'Re Evaluating the Success of a Brand on Mobile
related talks
43mResponsive Design, Past, Present and Future
40mThings To Keep In Mind When Working In The World Of Responsive Design
43mGetting serious about Responsive Web Design
25mFor a Future-Friendly Web
50mLaziness in the Time of Responsive Design
43mDeclarative Design
53mFuture Perfect Tense
48mResponsive Design Workflow