Everybody is talking about Responsive Webdesign, and rightfully so. But really, it is only a small part of the problem, and actually the easy part. What if there's no screen at all? Or no keyboard or mouse? How do you prepare for future devices? Actually, it's easy: HTML is accessible and semantic by default. In the end it boils down to this: first we need to start from great content, then we make it fast and accessible (through semantic HTML or an API), continuing to create a contextualized experience for specific user groups, and finally, make it fancy. Start using HTML5 semantics today, and make any design decisions wisely.
Dave Shea – Responsive anti patterns- Once you ship a mobile site or responsive site, -> average 100% increase in sales within weeks. No more photoshoponly. Decide and mockup in the browser (Stephen Hay – Revenge of the web) Design is hard to get right everywhere, sosimpler design these days (see MS, Apple ?) The fold is back Tables are hard
72 % of sites send all visitorsroughly the same dataSmall screen != smallbandwidthLarge screen != high bandwidth
Anna Debenham – Console browsersOrwhenit has touch instead of amouse? (Peter-Paul Koch – Developing for touch)Or when it’s black-white? (e-readers)
Well described and structured content without presentation served through a decent API is essential. (Josh Clark – Beyond mobile)Sara Wachter-Boettcher – Designing with and for existing content- Content structure is the foundation of any website. To do this right it requires an organisational shift to also keep content structured.- Try to reduce content before starting anything else (design, development, etc.). This process not only makes production easier but also gives great insight into organisational structure.
- HTML is made foraccessibility (Derek Featherstone – Doing responsive right)Even DOM events are! Stick with click! (Peter-Paul Koch – Developing for touch) HTML5 adds so many semantic possibilities
CennyddBowles – Context, bloody contextDeviceEnvironmentTimeActivityIndividualLocationSocialOther devices (Josh Clark – Beyond mobile)Apps are such a enrichmentfor a specificdevice. Butthey’reonlyanenrichment!Thus, the discussion “native versus HTML5” is really NOT important at all. Usewhatyoulike. Re-use is good, perfect UX is good as well.
Big examples: Windows and Apple. Go back to the basics. Itneeds to workeverywhere and with/without touchSo design becomessimple and consistent