At a meeting of the Interaction Designer’s Association (IxDA) one of the audience members, during the Q&A, asked “Why are we all making websites?”
What a fantastic question. We primarily consider the digital at the Institute, and the way that discourse is changing as it is presented on screen and in the network. But the question made me reevaluate why a website is the form I immediately think of for any new project. I realized that I have a strong predilection for websites because I love the web, and I know what I’m doing when it comes to sites. But that doesn’t mean a site is always the right form for every project. It prompted me to reconsider two things: the benefit of Sophie books, and the position of print in light of the network, and what transformations we can make to the printed page.
First, the Sophie book. It’s not a website, but it is part of the network. During the development and testing of a shared, networked book, we discovered that there a particular feeling of intimacy associated with sharing Sophie book. Maybe it’s our own perspective on Sophie that created the sensation, but sharing a Sophie book was not like giving out a url. It had more meaning than that. The web seemed like a wide-open parade ground compared to the cabin-like warmth of reading a Sophie book across the table from Ben. Sophie books have borders, and there was a sense of boundedness that even tightly designed websites lack. I’m not sure where this leads yet, but it’s a wonderfully humane aspect of the networked book that we haven’t had a chance to see until now.
On to print. One idea for print that I find fascinating, though deeply problematic, is the combination of an evolving digital text with print-on-demand (POD) in a series of rapidly versioned print runs. A huge issue comes up right away: there is potentially disastrous tension between a static text (the printed version) and the evolving digital version. Printing a text that changes frequently will leave people with different versions. When we talked about this at the Institute, the concern around the table was that any printed version would be out of date as soon as the toner hit the page. And, since a book is supposed to engender conversation, this book, with radical differences between versions, would actually work against that purpose. But I actually think this is a benefit from our point of view—it emphasizes the value of the ongoing conversation in a medium that can support it (digital), and highlights the limitations of a printed text. At the same time it provides a permanent and tangible record of a moment in time. I think there is value in that, like recording a live concert. It’s only a nascent idea for an experiment, but I think it will help us find the fulcrum point between print and the network.
As a rider, there is a design element with every document (digital or print) that makes the most of the originating process and creates a beautiful final product. So a short, but difficult question: What is the ideal form for a rapidly versioned document?