Free Trial

Safari Books Online is a digital library providing on-demand subscription access to thousands of learning resources.


  • Create BookmarkCreate Bookmark
  • Create Note or TagCreate Note or Tag
  • DownloadDownload
  • PrintPrint
Share this Page URL
Help

Epilogue

Epilogue

Limitations encourage creativity.

Never rue the limitations of a design problem—a too small site, an inconvenient topography, an overlong space, an unfamiliar palate of materials, contradictory requests from the client...Within those limitations lies the solution to the problem.

—Matthew Frederick, 101 Things I Learned in Architecture School, #97

P3.1. And in the End...

In the preceding pages, we have covered patterns about self (Identity, Presence, Engagement, and Reputation), patterns about social objects (Collecting, Sharing, Broadcasting and Publishing, Feedback, Communication, Collaboration, and Social Search), and patterns about the social graph and location (Personal Connections, Community Management and Place, Geography, Location). We have shared patterns about community management, licensing, and open standards. We have also given you some food for thought in a set of overarching principles: Talk Like A Person, Design for Everyone, Be Open, The Ethical Dimension, and others.

And finally, we acknowledge in this book’s last chapter that not everyone is designing social web interfaces for the average consumer in the United States. There are facets and contexts of delivery medium (web, mobile, device); business or consumer; age (youth, elderly, everyone in between); and other factors that will color how you approach your design and what patterns to pay attention to and which to leave in the toolbox.

The landscape of social interactions is as broad as it is deep, and—as we have touched on briefly in the last chapter—complicated and flavored by different delivery mechanisms, contexts, and user types. Designing for this space is complicated but also a lot of fun. It’s important to remember that the social experience can be quite extraordinary, even with the simplest of interfaces (remember the BBSes we mentioned in the beginning?). Pick and choose thoughtfully, and put the patterns together like a recipe or a poem, knowing that you can always start simple and expand as you go. Much of what we can do as designers is really about building a space for something to happen and then getting out of the way.

Are We Building a Better Internet?

When was the last time you fought for good user experience against shortsighted business goals? How about delaying a development schedule to get a a feature right? Or redesigned a major section of your site to make tomorrow’s Internet a better place? I bet you were with me until the last question.

The Internet has no absolute authority on right or wrong. No Pope, Czar, or Commander in Chief. Yet, like the flutter of a butterfly’s wing that creates a hurricane halfway around the world the small design decisions we make today shape tomorrow’s Internet. Our decisions can welcome a new digital utopia or reinforce an Internet that teaches its citizens to be jaded, narcissistic, and paranoid. The choice is ours.

For a long time, the ever-expanding Amazon.com top-tab navigation was the Internet’s most successful design meme. Although Amazon.com abandoned it, many sites still employ top-tab navigation doppelgangers. This was a fairly harmless design meme in the scheme of things. I was never a huge fan, but, besides offending my sense of good design, it probably didn’t do much to damage the overall Internet. Until the advent of social applications, most design memes fell into this category: at worst, they were a drag Now we’re facing a different worst-case scenario. Users are storing their most intimate data in the cloud, social media is incestuously interconnected, and application creators (like yourselves) are eager to reuse design elements across the Internet. We’re creating hyper-replicating design memes with the potential to do real harm. Replace “design meme” with “evil alien virus,” and you’ve got yourself a pitch for an action-packed Hollywood blockbuster.

The first design meme I encountered with true deleterious power was the opt-out checkbox for marketing emails on sign-up forms. Our argument for it to be opt-in instead was userexperience-focused with a nod to the business folks. Undesired emails would hurt the brand annoy the user, and not necessarily generate qualified leads. What we didn’t consider back then was how that small decision would help create today’s Internet. These undesired marketing emails—along with the invention of V1@gra—contributed to the cacophony of commercial noise that now pollutes the Internet. As far as I know, this noise hasn’t killed anyone. Yet most of us would prefer the Internet to feel a little more like relaxing on a secluded beach with a good book and less like Times Square on a muggy Saturday night.

Imagine for a moment what today’s design decisions will do to mold the Internet’s future. What if every product decision you made last week became a successful design meme? Would that create an Internet where you’d want your kids to play?

Sometimes we get lucky and it’s not difficult to discern the difference between right and wrong. Don’t sell user data because you’re short on beer money. Don’t keep emailing users af er they unsubscribe. Don’t read user emails to find the next great stock pick. These are certainly over-simplified dilemmas, and sadly, most ethical dilemmas aren’t as clear-cut.

One of the great advances in the Internet was integrating disparate systems to produce new products. The early Google Maps mashups opened the door for complex social applications that found new uses for personal information stored in the cloud. Gathering this personal social data is not as simple as displaying Craigslist apartment rentals on a Google Map. Social sites secure user data using credentials, such as a unique ID and password, a design pattern introduced in the earliest computer systems. Some products allow third parties to securely access user data, although the experience is often frustrating. Many don’t even bother to make such allowances. When it’s a choice between no access and a poor use experience, it may seem reasonable to request a user’s credentials from another site. After all, can’t you create a better user experience if you can control the experience? Sadly, this design meme is training users to feel comfortable giving out their passwords to anyone who asks nicely. Identity theft is already a major problem, and training users to be sheep certainly won’t help.

The ethical solution for accepting other sites’ credentials is easy. All products should be built on open standards with a complete set of secure APIs using common design interfaces. Let’s universally employ an un hackable icon to denote that entering your credentials is 100% guaranteed secure. Any site that refuses to participate will be shut down instantly. Then we can all hold hands on a picturesque hillside and sing “I’d like to buy the world a Coke.”

Unfortunately, what is truly best for the Internet’s future may not always be realistic. The challenge in this case is to develop standard interfaces to allow third-party access while teaching users responsible identity protection. The solutions become even more onerous when we con sider that not every site will adopt the ethical standard. Tomorrow’s Internet relies on sharing data across products. However, we don’t want to achieve this at the expense of our user’s security. A sense of security breeds trust, and trust breeds openness and understanding—all valuable attributes for tomorrow’s Internet.

To complicate matters, sometimes it’s a decision between two undesirable outcomes. A user’s freedom of speech is wonderful until it’s focus ed on making another user miserable. I tend to lean anti censorship, but am I willing to design the systems to ensure that my site doesn’t make cyber-bullying worse? Will I take the time to consider nascent destructive trends and go out of my way to build systems to prevent them from maturing? Is this even a good use of my time, considering I may mistakenly choose to address an ultimately innocuous trend?

Even when the perfect solutions don’t exist, we need to add the ethical questions to our product conversations. Will this decision do anything to make the Internet worse? Better? If everyone else did the same thing, would I ever log on? These conversations should certainly occur in the greater industry (and in fine books like this one). More importantly, we need to include the ethics discussion in our everyday product design meetings.

there’s a lot of guesswork involved. We need to put on our futurist hats and look into our crystal balls to see what we’re creating. Our predictions may fall flat. We may not always comprehend the full extent of our decisions. But to ignore ethics in our product discussions is the equivalent of accepting that we have no power or influence over the future. I, for one, am in this industry to create products that help people fulfill their personal potential and ultimately make the world a better place. It’s a lot of gravitas for seemingly insignificant product decisions, but I believe in the power of the Internet, and I want to be on the right side of history.

Today’s Internet has revolutionized the way the world communicates. We are living in a time of unprecedented access to information, and so many barriers of the past are receding. Conversely, today’s Internet not only replicates atrocities from the offline world, but it makes them easier to commit. Child abuse, sexual predators, bullying, and identity theft come quickly to mind

Skynet may be waiting around the corner to render all our efforts moot, but until that day we need to accept the responsibility to build an Internet that can make us all proud. Critically examining our decisions on ethical grounds alone won’t solve all the problems of tomorrow’s Internet. But acknowledging that seemingly small design decisions are the foundation of tomorrow’s Internet is a valuable first step in accepting ownership of the future.

—Matte Scheinker, matte.org (http://matte.org)


The collection of patterns in this book is just the beginning of a conversation. What started on whiteboards, in barcamps, and on listservs is collected in this book and on our site wiki. We invite you to join us at our website, http://www.designingsocialinterfaces.com, to continue the conversation. We are interested in hearing your stories about designing for this space and what patterns have been most successful, which ones need more work, which should be tossed out entirely because the world has moved beyond them, and which new and emerging interactions might be added to the library.

As we mentioned in the beginning, we approached this as a pattern language, and like any language, this is a living, evolving, and ever-changing beast.

As Christopher Alexander writes in A Pattern Language

This language, like English, can be a medium for prose or a medium for poetry. The difference between prose and poetry is not that different languages are used, but that the same language is used differently. In an ordinary English sentence, each word has one meaning and the sentence too, has one simple meaning. In a poem the meaning is far more dense. Each word carries several meanings; and the sentence as a whole carries an enormous density of interlocking meanings, which together illuminate the whole.

The same is true for pattern languages. It is possible to make buildings by stringing together patterns in a rather loose way. A building made like this, is an assembly of patterns. It is not dense. It is not profound. But it is also to put patterns together in such a way that many many patterns overlap in the same physical space; the building is very dense; it has many meanings captured in a small space; and through this density, it becomes profound.

Why not try for that lyric quality, the quality without a name, in the spirit of Alexander?