Designing in the Browser
Heads up, the following is a technical reflection blog post. I do a lot of web development after all.
Launched the SVA MFA Interaction Design Thesis Festival website on Tuesday. Another foray into responsive design, using Andy Clark’s 320andUp framework. From receiving the basic identity and content structure to launch, the site took about five days.
The website is relatively straight forward, just a list of thesis profiles, plus a couple ancillary page. Since the site was so simple, I took the opportunity to try out some new approaches. Firstly, I went straight for a responsive design, and secondly, I decided to completely skip designing in photoshop, and went directly to design in browser.
I must admit I flailed around a bit before landing on a workable iterative process. As usual, I began with thinking through content hierarchy, and main flows of experience through the site.
The two main scenarios in my head were focused on visitor browsing through the thesis projects, and festival attendees looking for event information. According to these scenarios I built out a basic content hierarchy.
The next task was to write the HTML. True to what I try to teach others, I began strictly with HTML content first, making sure that each page template will read write without styling or layout. This was particularly important since I was taking a mobile-first approach. Forcing myself to put together the content hierarchy first ensured the site communicates clearly.
Basic typography came next, and this is where I began to run into trouble. I had no strict forward process for this, except to address each device size, from small to large, and circle back as inspiration leads to changes and iteration. From typography I expanded outwards, polishing the layouts and making small aesthetic and usability adjustments. Throughout this process there was a rapid back and forth between CSS changes and browser refreshes. The responsive.html file Andy included in 320andup was very valuable here. (As was a second monitor.)
Designing in the browser was great for evolutionary, iterative improvements. For a project this small, with such a short turn around time, this approach worked well. I stuck to a tried-and-true two-column layout above 768px, and simply polished it as best I could while keeping with responsive design principles. I imagine in a bigger, more extensive project, I would want to experiment with more radical variations. I am not sure those variations would be as quick to do in the browser as it would be through a graphic program.
There is one big flaw in this process. All the testing I did were hallway tests, mostly with other interaction designers. I guess I will walk around the thesis festival and see how (and if) people visit the site on the mobile phone as I imagined. The other big down fall for the site is the lack of a responsive image strategy, since the imagery is such a big part of the site. I need to read up on what is the latest in responsive image delivery soon - anyone have good suggestions?
The thesis festival is tomorrow, May 12th. My seniors have done some really awesome projects. Will you come and hear from them? Check out their projects here: http://interactiondesign.sva.edu/festival/2012.




2