As a designer, you conceive your design with the core values of a project in mind; you strive to reflect the ideas and feelings behind it. Contrary to that, the first lesson in web development is always separate your design from your code. It’s important that projects be flexible. A myriad number of screen sizes and devices mean the “presentation layer” should be designed to change, particularly when you use web technology. Moreover, partnerships will impact your design.
Aaron and I have been making websites for 15 years, so we get that. Most people don’t know it, but what we’ve built at BookGlutton is flexible in many ways. Easiest to change is the look and feel. Over the years we’ve had a number of conversations about offering our “BookClub in a Can,” the ability to export the social experience to other sites, so they can curate their own book clubs. Business considerations and content deals ultimately kept these projects from launching, and BookGlutton remained a destination site. But it’s fascinating to see how associating the reading experience with a different brand affects your relationship to it.
Skinning the Reader takes almost no time at all. However, it changes the experience significantly. The Reader takes on the trappings of that community.
All the mockups listed here preserved the buttons and layout, but even that can change. It makes for interesting consideration. Sometimes these mockups were presented in meetings; sometimes the discussion ended prematurely. See more skins, as well as the original BookGlutton design on Flickr.