DESIGN’S future is in your hands. Designing For Touch by Josh Clark (foreword by Brad Frost) guides you through the new frontier in design.
I’ve been a fan of Josh Clark’s since before he was “Josh Clark”—back when he invented Couch to 5K, and gave it away with no strings (or copyrights or trademarks or patents, Lord help us) attached. And I’ve followed Josh’s career as an interaction design consultant, public speaker, and author. Guy’s got it all: intelligence, perspective, and the ability to not just communicate, but persuade. He’s a down-to-earth futurist with old-fashioned showmanship. And all that Josh Clark goodness has found its way into his new book.
Josh genuinely wants designers to not only keep up with the touchscreen but also to reimagine it. Designing For Touch will teach novice and seasoned designers alike about ergonomic demands (and rules of thumb), layout and sizing for all gadgets, an emerging gestural toolkit, and tactics to speed up interactions and keep gestures discoverable. You’ll get the know-how to design for interfaces that let your users touch—stretch, crumple, drag, flick—information itself. And the inspiration to take touch to the next level.
Ethan told the world that Responsive Web Design required, and was defined by, fluid layouts, flexible images, and media queries. All three elements had to be present. If they weren’t using all three, you might be doing something interesting, but you were most definitely not doing Responsive Web Design.
Ethan invented all of this. Without him, we would likely be arguing whether it was time to consider 1280 pixels the new default fixed width for all desktop websites, and sending anything that wasn’t a desktop browser to a function- and content-limited “mobile site” whose URL began with the letter m. Ethan is a brilliant, multi-talented innovator; I am but the shadow of a hack. And yet, before he began creating his book, midway through the writing, and even a year after I published it, I continued to urge Ethan to rethink #RWD as “a bigger idea”—a concept rather than a single set of techniques.
I’m no genius. What I meant by “bigger idea” was limited to the notion that we’d one day be able to create responsive layouts with different techniques—so let’s not restrict the concept to a particular execution. I wasn’t thinking about other meanings of responsive, wasn’t considering problems of responsive content, and so on. I’m not that forward-thinking and it was three freaking years ago, come on.
I lost my gentle argument with Ethan, so the industry is having it now. And that’s just as it should be. Everything worked out for the best. Here’s why:
If Ethan hadn’t included three simple executional requirements as part of his definition, the concept might have quickly fallen by the wayside, as previous insights into the fluid nature of the web have done. The simplicity, elegance, and completeness of the package—here’s why, and here’s how—sold the idea to thousands of designers and developers, whose work and advocacy in turn sold it to hundreds of thousands more. This wouldn’t have happened if Ethan had promoted a more amorphous notion. Our world wouldn’t have changed overnight if developers had had too much to think about. Cutting to the heart of things and keeping it simple was as powerful a creative act on Ethan’s part as the “discovery” of #RWD itself.
Some commenters want to use initial-capped Responsive Web Design to mean responsive design as Ethan first defined it, and lowercase responsive design to mean an amorphous matrix of exciting and evolving design thinking. Lyza says soon we’ll stop saying Responsive altogether, a conclusion Andy Clarke reached three years ago.
Me, I like that Ethan stuck to his guns, and that the classical definition will always be out there, regardless of how web design evolves thanks to it. Kind of like there’s HTML 5, a defined and scoped W3C specification, and HTML living standard, an evolving activity. Our industry needs roots and wings, and, lucky us, we’ve got ’em both.
Big Web Show ? 102: Sass for Web Designers with Dribbble’s Dan Cederholm
DESIGNER, developer, banjoist, Dribbble co-founder, and all-around nice guy Dan Cederholm and I discuss fear of CSS pre-processors; the craft of code; growing the Dribbble design community; transitioning from a two-person part-time start-up to a full-time company with employees; and Dan’s new book Sass For Web Designers in Episode ? 102 of The Big Web Show on Mule Radio.
While historically, it’s been difficult at best to create print-quality PDF books from markup alone, CSS3 now brings us the Paged Media Module, which targets print book formatting. “Paged” media exists as finite pages, like books and magazines, rather than as long scrolling stretches of text, like most websites. With a single CSS stylesheet, publishers can take XHTML source content and turn it into a laid-out, print-ready PDF. You can take your XHTML source, bypass desktop page layout software like Adobe InDesign, and package it as an ePub file. It’s a lightweight and adaptable workflow, which gets you beautiful books faster. Nellie McKesson, eBook Operations Manager at O’Reilly Media, explains how to build books with CSS3.
Grizzled job hunting veterans know too well that a sharp résumé and near-flawless interview may still leave you short of your dream job. Competition is fierce and never wanes. Finding new ways to distinguish yourself in today’s unforgiving economy is vital to a designer/developer’s survival. Happily, web standards whiz and mobile web developer Andrew Hoffman has come up with a dandy differentiator that is just perfect for A List Apart readers. Learn how to author a clean résumé in HTML5/CSS3 that scales well to different viewport sizes, is easy to update and maintain, and will never grow obsolete.
IN A GORGEOUSLY PACED ESSAY at n+1, “the magazine that believes history isn’t over just yet,” an amazing young (22?) writer named Alice Gregory reviews a novel by Gary Shteyngart while simultaneously describing her exhausted and shattered mental life as a Twitter- and Tumblr-following, iPhone-carrying, socializing-while-isolated Internet addict, i.e. modern young person:
This anxiety is about more than failing to keep up with a serialized source, though. It’s also about the primitive pleasure of constant and arbitrary stimulation. That’s why the Facebook newsfeed is no longer shown chronologically. Refresh Facebook ten times and the status updates rearrange themselves in nonsensical, anachronistic patterns. You don’t refresh Facebook to follow a narrative, you refresh to register a change—not to read but to see.
And it’s losing track of this distinction—between reading and seeing—that’s so shameful. It’s like being demoted from the category of thinking, caring human to a sort of rat that doesn’t know why he needs to tap that button, just that he does.
Sometimes I can almost visualize parts of myself, the ones I’m most proud of, atrophying. I wish I had an app to monitor it! I notice that my thoughts are homeopathic, that they mirror content I wish I weren’t reading. I catch myself performing hideous, futuristic gestures, like that “hilarious” moment three seconds into an intimate embrace in which I realize I’m literally rubbing my iPhone screen across his spine.
Progressive enhancement: all you need to know is here
ONE GLORIOUS AFTERNOON in March, 2006, as a friend and I hurried past Austin’s Downtown Hilton Hotel to catch the next session of the SXSW Interactive Festival, a young stranger arrested our progress. With no introduction or preliminaries, he announced that he was available to speak at An Event Apart, a conference for web designers that Eric Meyer and I had launched three months previously. Turning to my companion with my best impression (which is none too good) of Mr Burns of “The Simpsons,” I asked, “Who is this brash young upstart, Smithers?”
The brash young upstart quickly became an essential colleague. In the months and years that followed, Aaron Gustafson created dazzling front- and back-end code for some of my agency’s most demanding clients. Just as importantly, he brilliantly tech-edited the second and third editions of Designing With Web Standards. The job largely consists of alerting Ethan Marcotte and me to the stuff we don’t know about web standards. I’ll let you think about that one. For five years now, Aaron has also been a tough but fair technical editor for A List Apart magazine, where he helps authors succeed while ensuring that they are truly innovative, that their methods are accessible and semantic, and (thanks to his near-encyclopedic knowledge) that they give all prior art its due. Moreover, Aaron has written seminal pieces for the magazine, and, yes, he has lectured at An Event Apart.
Given my experiences with the man and my admiration for his knowledge and abilities, I was thrilled when Aaron told me the premise of this book and began letting me look at chapters. This isn’t just another web design book. It’s an essential and missing piece of the canon. Our industry has long needed a compendium of best practices in adaptive, standards-based design. And with the rise of mobile, the recent significant improvements in desktop and phone browsers, and the new capabilities that come with HTML5, CSS3, and gestural interfaces, it is even more vital that we who make websites have a reliable resource that tells us how to take advantage of these new capabilities while creating content that works in browsers and devices of all sizes and widely differing capabilities. This book is that resource.
The convergence of these new elements and opportunities is encouraging web professionals to finally design for the web as it always should have been done. Adaptive design is the way, and nobody has a wider command than Aaron of the thinking and techniques required to do it well. In these pages you will find all that thinking and those methods. Never again will you lose a day debating how to do great web design (and create great code) that works for everyone. I plan to give this book to all my students, and to everyone I work with. I encourage you to do likewise. And now, enough preliminaries. Dive in, and enjoy!
Episode 38: Macworld’s Jason Snell live on The Big Web Show
Macworld editorial director Jason Snell is our guest on The Big Web Show (“Everything Web That Matters”) Episode #38, recording live Thursday, February 10, at 12:00 PM Eastern. Jason, co-host Dan Benjamin and I will discuss the future of publishing, Macworld’s evolving digital strategy, and of course our favorite computers, phones, apps, and tablets.
Jason Snell is editorial director of Macworld. He’s been covering Apple since 1994. He’s also the host of The Incomparable Podcast, at theincomparable.com.
The Big Web Show (“Everything Web That Matters”) records live every Thursday at 12:00 PM Eastern. Edited episodes can be watched afterwards, often within hours of recording, via iTunes (audio feed | video feed) and the web. Subscribe and enjoy!
“It’s been a great year for web design books; the best we can remember for a while, in fact!” So begins Goburo’s review of the Top Web Books of 2010. The list is extremely selective, containing only four books. But what books! They are: Andy Clarke’s Hardboiled Web Design (Five Simple Steps); Jeremy Keith’s HTML5 For Web Designers (A Book Apart); Dan Cederholm’s CSS3 For Web Designers (A Book Apart); and Eric Meyer’s Smashing CSS (Wiley and Sons).
I’m thrilled to have had a hand in three of the books, and to be a friend and business partner to the author of the fourth. It may also be worth noting that three of the four books were published by scrappy, indie startup publishing houses.
Congratulations, all. And to you, good reading (and holiday nerd gifting).
Blue Beanie Day Haiku Contest – Win Prizes from Peachpit and A Book Apart
ATTENTION, web design geeks, contest fans, standards freaks, HTML5ophiles, CSSistas, grammarians, bookworms, UXers, designers, developers, and budding Haikuists. Can you do this?
Do not tell me I
Am source of your browser woes.