The Last Three Entries:
The web isn’t a “platform” like a native OS: it’s a continuum. Varying support levels work with progressive enhancement.
As he usually does, Jeremy put words to something that’s been bugging me for some time.
As I see it: we play the long game in this business. Standards get authored, browsers implement them (often at a varied, staggered pace), and, over time, we learn to rely on them in our work.
Despite that, we keep getting hung-up on perceived short-term failings in various browsers. No, IE6 doesn’t have
document.querySelectorAllsupport; no, we don’t have wide in-browser access to a user’s camera; no, there isn’t a way to reliably detect touch; no, we don’t have reliable insight into the user’s “context.”
Often, that leads to people deciding the web is being “held back.” So there’s some hopscotching of, say, progressive enhancement—which, in addition to being a great philosophy, has been shown to have real, practical benefits to businesses—in favor of “not being held back.” So, in response, we make the same arguments—good and great arguments, mind, but we’ve been making them for some time now.
I don’t really have any answers here—hell, I’m not entirely sure what I’m griping about. But I do wonder if our collective short-term frustrations leads us to longer-term losses. And seeing the web not as a “platform” but as a “continuum”—a truly fluid, chaotic design medium serving millions of imperfect clients—might help.
I mean, ages ago John Allsopp wrote about “[embracing] the ebb and flow of things” on the web. But it’s taken me some fourteen years to realize he wasn’t just talking about layout: our attitude toward the web has to be as flexible as our designs. And maybe it’s worth remembering that the web’ll get there, eventually—we just need to keep playing that long game.
In the past few years, in speaking with client companies and colleagues, the one thing that comes is that responsive web design doesn’t begin and end with CSS. The best responsive sites are founded upon a culture of performance; they’re made with iterative design and development practices; they plan for accessibility and progressive enhancement from the outset; and they are, perhaps most importantly, built upon a well-researched and -executed content strategy.
In other words, successfully designing responsively isn’t just about fluid grids and media queries: it’s about designing a better process. And that’s the challenge Karen and I find really, really interesting. (And as it happens, we have a bunch of ideas on the topic, too.)
To that end, we’ve designed a workshop to share the many things we’ve learned about responsive design and mobile content strategy over the course of one day or two. And we want to share them with you and your company.
If all this sounds interesting to you, we happen to have a little website with a bit more detail. Check it out; we’d love to hear what you think.
It seems to be the season for presentation tips. First, Mark had a handy hit-list of tips for speakers and audience members. Then, Andy shared a few easy tips for prettying up one’s default slide designs. And then, Rands noted a test slide for your deck isn’t the worst idea. (In fact, I goddamn love it; Tim Brown’s already made a Keynote-ready template available.)
If you can’t guess, I fucking love this.
See, I’m not formally trained in web design or public speaking—and in both arenas, the best education I’ve gotten is watching really talented people work. My presentation style’s changed considerably over the years, as the likes of Kristina Halvorson, Karen McGrane, Jeff Veen, Doug Bowman, Erin Kissane, and Dan Cederholm have been hugely influential on my own style. I’d watch them work, and try to figure out what I liked about their style, and why I liked it. And then I’d try to be better the next time I was onstage. And heck, when people write about how they work, well—that’s just damned grand.
All that said, I don’t have any significant tips to add to the above, but thought I’d list two things I find especially helpful. One’s semi-philosophical; the other, less so.
Eliminate dependencies in your work. I try to ensure my presentations aren’t reliant on audio or a network connection. Basically, depending on where you’re speaking, it’s entirely possible either—or both!—of those things won’t be available to you. So this usually means that if I want to show the audience how a certain page might work, I’ll record a little screencast, rather than assuming I can jump out of Keynote into the browser. (I use the idiosyncratic-as-hell ScreenFlow, but any ol’ app will do.)
In other words: by all means, use audio in your presentation, or incorporate online demos! But if you do, make sure you’re planning for failure, and have a contingency plan at the ready. (I guess you could see this as a corollary to progressive enhancement, but in Keynote form.)
Pack a bag. Related to this, I have a small satchel inside my laptop bag. In it, there is:
- One VGA adapter for my MacBook Air.
- One USB presentation remote. (There are many such remotes available. You want this one.)
- Fresh backup batteries for that remote.
- A USB ethernet adapter for my MacBook Air.
In other words, this is the stuff my computer needs to actually run the presentation I’ve prepared.
Now, most conference organizers will have many of these things, but I don’t want to expect that they will. They’re busy folks, after all. In other words, I want to ensure I’m the only one responsible for the quality of my presentation, and packing a small bag of critical cords and adapters helps me do that.
(As a bonus, I’ve started traveling with a short (6") VGA cable, rolled up and tucked into a large, rarely-used pocket of my laptop bag. This has been supremely handy for doing run-throughs on hotel room TVs the night before a talk.)