I’ve been thinking about workflows for Responsive Web Design quite a bit, particularly since its now become our default approach on every new project – similar to Cloud Fours recent change of heart. I’ve been especially influenced by two recent articles on the topic, namely Dennis Kardys’s A More Flexible Workflow, and Viljami Salminen’s Responsive workflow.
I struggled a bit to make their approaches fit into how we worked, so I decided to expand on what they’ve done and draw something that reflects a bit more accurately how we are incorporating Responsive Web Design into a user-centered workflow within an agency model. It’s not perfect by any means, but here’s what I came up with.
Ultimately, we are deluding ourselves if we think that the products that we design are the ‘things’ that we sell, rather than the individual, social and cultural experience that they engender, and the value and impact that they have. Design that ignores this is not worthy of the name. Design should embrace failure.
Stephanie Troeth’s main job title is subtly different from the terms we usually hear within the field of user experience. She’s a user experience strategist, a discipline that “has yet to hit mainstream”, she tells me, which involves working in the place where user experience and business objectives meet. She will go into gut instincts more in this interview.
There is a very clever technique by Alexey Ten on providing an image fallback for SVG going around the internet recently. It does just what you want in the classic no-SVG-support browsers IE 8- and Android 2.3. If we dig a little deeper we find a some pretty interesting stuff including a bit of unexpected behavior that is a bit of a bummer without SVG fallbacks.
Many software developers fail to understand the principles of designing notifications the right way. It sounds like a simple feature, but when you look at it from the end–user’s perspective, there are some important things that need good execution.
If you’re building a product, you have to be great at saying No. Not ‘maybe’ or ‘later’. The only word is No. Building a great product isn’t about creating tonnes of tactically useful features which are tangentially related. It’s about delivering a cohesive product with well defined parameters.