2006 DOESN’T seem forever ago until I remember that we were tracking IE7 bugs, worrying about the RSS feed validator, and viewing Drupal as an accessibility-and-web-standards-positive platform, at the time. Pundits were claiming bad design was good for the web (just as some still do). Joe Clark was critiquing WCAG 2. “An Inconvenient Truth” was playing in theaters, and many folks were surprised to learn that climate change was a thing.
I was writing the second edition of Designing With Web Standards. My daughter, who is about to turn twelve, was about to turn two. My dad suffered a heart attack. (Relax! Ten years later, he is still around and healthy.) A List Apart had just added a job board. “The revolution will be salaried,” we trumpeted.
Preparing for An Event Apart Atlanta, An Event Apart NYC, and An Event Apart Chicago (sponsored by Jewelboxing! RIP) consumed much of my time and energy. Attendees told us these were good shows, and they were, but you would not recognize them as AEA events today—they were much more homespun. “Hey, kids, let’s put on a show!” we used to joke. “My mom will sew the costumes and my dad will build the sets.” (It’s a quotation from a 1940s Andy Hardy movie, not a reflection of our personal views about gender roles.)
Jim Coudal, Jason Fried and I had just launched The Deck, an experiment in unobtrusive, discreet web advertising. Over the next ten years, the ad industry pointedly ignored our experiment, in favor of user tracking, popups, and other anti-patterns. Not entirely coincidentally, my studio had just redesigned the website of Advertising Age, the leading journal of the advertising profession.
Other sites we designed that year included Dictionary.com and Gnu Foods. We also worked on Ma.gnolia, a social bookmarking tool with well-thought-out features like Saved Copies (so you never lost a web page, even if it moved or went offline), Bookmark Ratings, Bookmark Privacy, and Groups. We designed the product for our client and developed many of its features. Rest in peace.
In short, it was a year like any other on this wonderful web of ours—full of sound and fury, true, but also rife with innovation and delight.
As part of An Event Apart’s A Decade Apart celebration—commemorating our first ten years as a design and development conference—we asked people we know and love what they were doing professionally ten years ago, in 2006. If you missed parts one, two, three, or four, have a look back.
Pinterest giveth, and Pinterest taketh away
AS MY design career has taken on more and more strategic and managerial freight, I’ve done less and less hands-on design. This year, I decided to change that. As part of my reimmersion, I found myself reading less, and absorbing visual information more. Enter Pinterest.
I’d played with the app when it first came out—who didn’t?—but it didn’t stick with me the way a handful of apps do. It didn’t become an obsession, and so I gradually forgot about it. That’s just how apps work for me. They’re heroin, or they’re nothing.
But the moment my days began filling with sketching, and coding, and Photoshop comping, the genius of Pinterest, and the addictive high it provides when used obsessively and compulsively, was revealed to me.
In borderline religious ecstasy, I became a Pinterest junkie, compelled to collect and catalog every artist I’ve ever loved—every type designer, illustrator, filmmaker, social absurdity, comic book character, and book designer; every half-forgotten cartoonist; every city or nation I’ve visited.
Using Pinterest not only revived long-dead visual design brain cells, it created new ones. Work-related layouts and color schemes came easier as I spent more and more “downtime” collecting and cataloging half-forgotten styles, genres, and artists—and discovering new ones.
I ♥ Pinterest
As part of this work—for work it is; call it “research” if you prefer—I spent hours rearranging Boards on my profile for maximum aesthetic effect and rhythm. And more hours choosing and replacing the cover illustration for each Board. (If you don’t use Pinterest, here’s a summary: it lets you pin any image you find on the web, or on your own computer desktop or mobile device, to a virtual whiteboard. Pinterest calls each whiteboard you create a “Board,” and each image you affix to it a “Pin.” Part of the fun comes from sequencing Boards on your profile for aesthetic or educational reasons; choosing the featured image for each Board is likewise important and fun.)
Until a few days ago, you could edit and re-edit the featured image for each Board whether you were using Pinterest on the web (that is, via desktop computer), your phone, or your tablet. Doing these things worked differently on the different devices—choosing the featured image was actually faster and less tedious on iPhone and iPad than it was on the web—but the functionality was available in all three places, because Pinterest recognized that brands exist between devices, and that folks interact with your service on different devices at different times, as they choose.
Likewise, until a few days ago, you could change the order of Boards on your profile via drag and drop whether you were using Pinterest on the web or your tablet. (Likely because of screen space constraints, this functionality was not available on iPhone, where the display of Board content necessarily differs from the more desktop-design-focused method used on the web and on iPad.) Users like me changed the order of Boards to create visual interest, set up ironic contrasts, create visual rhythms up and down the screen, and so on. I’m a designer. I have my ways. These details are important to me—and, I imagine, to many other users, since Pinterest is a drug for visual obsessives.
An unexpected change
Then, a few days ago, Pinterest released an update that removed this functionality from the iPhone and iPad (and, I’m assuming, from Android as well). There was no blog post announcing the change. And no rationale offered for taking away features that mattered a lot to users like me. Pinterest knows these features matter, because Pinterest has our data. That’s the difference between making a digital product folks interact with via the internet, and making, say, a toilet plunger. If I manufacture toilet plungers, I can make assumptions about how folks use my product, but I probably don’t have much real data. If I make an application people use via http, I know everything.
Now, it’s not like people were complaining about the ability to edit their Boards: “We have too much freedom! This software provides too many delightful functions. Please remove two of them. But only from my mobile device.”
No. The features are still there on the website. So Pinterest knows people like these features.
And it’s not like the features are too difficult to put into mobile devices, since they already existed in those mobile devices.
A failure to communicate
You may ask why I’m telling you all this instead of telling it to Pinterest. Good question. The answer is, I tried telling Pinterest, but they don’t provide a forum for it. And that is the biggest problem. A company that makes products people love should have a way to communicate with those people. Not grudgingly offer them a few character-limited form fields on a “survey” page that isn’t even referenced in the site’s navigation.
When the features stopped working on my iPhone and iPad, I assumed something had gone wrong with my apps, so I deleted and reinstalled them. (Remember, there was no announcement; but then why would any company announce that it was taking away loved features for no apparent reason?)
When deleting and reinstalling didn’t help, I sought help and contact pages on Pinterest (and was only able to find them via third-party search engine).
In trying to file a bug report, I ended up in a pleasant (but confusing) conversation with a very nice Pinterest employee who explained that I wasn’t experiencing a bug: the software engineers had made a conscious decision to remove the functions I use every day … and had no intention of restoring them. She wasn’t able to tell me why, or point me to a URL that would offer a rationale, but she did tell me I could use Pinterest’s “Recommend a feature” form to “recommend” that the software engineers put those features back.
Since “Recommend a feature” is hidden from site navigation, the kindly person with whom I was in dialog provided a link where I could type in a few characters requesting that Pinterest restore the “drag Board order” functionality. There wasn’t room in the form fields to explain why I thought the feature should be restored, but at least I was able to make the request. The form asked if I was a Business account user, which I am. I don’t remember when or why I bought the Business tier of service. Maybe for the analytics. Maybe just because, as someone who makes stuff myself, I choose to pay for software so I can support the good people who make it, and do what I can to help their product stick around.
(It’s the same reason I remained a Flickr Pro user even after Yahoo gave the whole world 2GB of photo storage space for free. If everything is free, and nobody pays, services you love tend to go away. Half of web history is great services disappearing in the night after investors were dissatisfied with only reasonable profits.)
I don’t know why my paid status mattered to Pinterest, but I couldn’t help feeling there would be a prejudice in favor of my comment if I checked the box letting them know I was a paying customer. Even though it was information they requested, checking the box made me feel dirty. I also wondered why they were asking me. I mean, don’t they know? I gave them the email address they use for my login. I was logged in. They know my status. Are they just checking to see if I know it, too?
There can only be one (feature request)
But I digress. Because here is the main point. The moment I submitted the tiny, inadequate form requesting the restoration of a recently removed feature, the site set a cookie and sent me a message thanking me for completing the “survey.” It wasn’t a survey, but I guess one task completion message is as good as another.
Then I tried to use the inadequate form to report my second concern—the one about the removal of the ability to choose a featured image for my Board. The way this had always worked on the tablet was far superior to the tedious, painstaking way it works on my desktop. On the tablet, you could scroll through all your images with the flick of a finger, select the image you wanted, and complete the task in a few seconds. On the desktop, you had to click your way through every image on your Board in reverse chronological order. It’s the difference between flicking through a calendar, and clicking backwards from today, to yesterday, to the day before yesterday, and so on. The tablet version was fast, easy, intuitive—you interact directly with your content; you can see all relevant content at a glance. The desktop version is cumbersome and 1999-ish. If I had to pick which platform must lose the functionality I relied on, I would not have chosen the tablet. No customer who used the feature in both places would.
But I wasn’t able to share even a few characters of this thought with Pinterest, because once you submit a “survey” requesting a feature, a steel wall in the guise of a cookie slams down, and you cannot make a second feature suggestion.
Not even the next day. (Which is today. Which I just tried.)
This is a love letter
And that is why, as a hardcore fan and user of Pinterest, a service I love and use compulsively, I am using the public web rather than Pinterest’s somewhat unhelpful help center, to share my request with the brilliant software engineers who create this fabulous product.
And with designers, because these are the mistakes we all make when we create products and content sites. We think we are all about the people who use what we create. But we are probably frustrating the pants off them with our arbitrary design decisions and inadequate customer feedback mechanisms.
THE WORLD has finally caught up with Been, Inc. Three years ago, this tiny start-up company shared my studio space in New York. Their product idea was remarkably original: instead of passively accepting the data collection and loss of privacy that comes with most ad networks on the web, what if people had a choice—to either block ads and third-party trackers entirely, or earn rewards for letting ads through?
The initial web-based product, playfully designed by Monkey Do, took the scariness and complexity out of tracking issues, and returned the decision making power to the consumer. Unfortunately, the mainstream web wasn’t ready for ad blocking, and consumers en masse either weren’t ready to think about privacy, or simply didn’t know the company’s value proposition because of its nonexistent marketing budget. (The only thing that kills products faster than no marketing is poor execution—although a handful of products have survived both.)
To stay afloat in the face of mass indifference, the company temporarily pivoted, using a portion of their technology to facilitate sharing of web content between consumers, much like the late lamented Ma.gnolia or Pocket’s new Recommended section. But where Ma.gnolia and Pocket were/are text-powered, the pivoted Been app was primarily visual, which helped it gain traction in the eduation market. Grade-school teachers and kids loved using the app for research projects—and their support helped the company stay in business long enough for the internet to catch up with their ideas.
Version 2.0 of their Choice app for iOS is the product of years of work on user privacy, data ownership, and control. iOS fans can download it at www.been.mobi/getv2edu.
The company’s site explains the push-button mechanics through which you can choose to block ads and third-party trackers in your apps and Safari, or earn rewards by letting ads through and sharing (strictly non-personal) information with Been. (Earn Mode is limited to US users for now.)
When I foolhardily put down my deposit on a New York studio that was larger and more costly than what I needed, my hope was that it would attract a like-minded community of designers and tech companies from whom I would learn and be inspired. That was certainly the case with my friends at Been! I wish them great success at helping to bring the changes our web needs.
Progressive Enhancement FTW with Aaron Gustafson
LONGTIME developer, lecturer, and web standards evangelist Aaron Gustafson and I discuss the newly published update to Aaron’s best-selling industry classic “love letter to the web,” Adaptive Web Design: Crafting Rich Experiences With Progressive Enhancement, 2nd Edition (New Riders, 2015) in Episode № 140 of The Big Web Show—everything web that matters.
Topics covered include: Aaron’s superhero origin story as a creator of progressively enhanced websites and applications; “we’re not building things we haven’t built on the web before;” “creating opportunities for people outside your comfort zone;” development in the world of Node.js; “every interface is a conversation;” “visual design is an enhancement;” “interaction is an enhancement;” nerding out over early web terminal interfaces; Microsoft, Opera, and more.
Sponsored by DreamHost, Braintree, and Thankful.
Save 35% off Aaron Gustafson’s Adaptive Web Design: Crafting Rich Experiences With Progressive Enhancement, 2nd Edition when you enter discount code AARON35 at checkout.
№ 139: Every Time We Touch—Josh Clark, author of “Designing For Touch”
TOUCH introduces physicality to designs that were once strictly virtual, and puts forth a new test: How does this design feel in the hand? Josh Clark’s new book, Designing For Touch, guides designers through this new touchscreen frontier, and is the launchpad for today’s Big Web Show conversation.
In a fast-paced, freewheeling conversation, Josh and I discuss why game designers are some of our most talented and inspiring interaction designers; the economy of motion; perceptions of value when viewing objects on touchscreen versus desktop computer; teaching digital designers to think like industrial designers (and vice-versa); long press versus force touch; how and when to make gestures discoverable; and much more.
Sponsored by DreamHost and BrainTree. Big Web Show listeners can save 15% when ordering Designing For Touch at abookapart.com with discount code DFTBIGWEB. Discount valid through the end of January 2016.
REBUILDING iTunes library from scratch over two days got app working again. Fine use of lazy weekend.
Had to sacrifice all custom playlists dating back to 2002, including An Event Apart playlists and delivery room mix from Ava’s birth.
Playlists still exist on old iPod but can’t be copied from it back to iTunes. (All software I’ve tried freezes & fails.)
Playlists still exist as code snippets inside .itl file in old iTunes folder, but numerous trials prove iTunes can’t launch from that folder any more. Thus I can’t temporarily launch from old folder, export playlists, switch back to safe new folder, and import them, thereby saving them.
And iTunes can’t import old .itl files. I Googled. I tried anyway.
13 years of custom playlists. From before, during, and after my marriage. Including one my daughter called “princess music” and danced to when she was three. Gone.
But, really, so what? Over time we lose everything. This loss is nothing. Attachment is futile. Always move forward, until you stop moving.
Publishing v. Performance—or, The Soul of the Web
MY SOUL is in twain. Two principles on which clued-in web folk heartily agree are coming more and more often into conflict—a conflict most recently thrust into relief by discussions around the brilliant Vox Media team, publishers of The Verge.
The two principles are:
Building performant websites is not only a key differentiator that separates successful sites from those which don’t get read; it’s also an ethical obligation, whose fulfillment falls mainly on developers, but can only happen with the buy-in of the whole team, from marketing to editorial, from advertising to design.
Publishing and journalism are pillars of civilized society, and the opportunity to distribute news and information via the internet (and to let anyone who is willing to do the work become a publisher) has long been a foundational benefit of the web. As the sad, painful, slow-motion decline of traditional publishing and journalism is being offset by the rise of new, primarily web-based publications and news organizations, the need to sustain these new publications and organizations—to “pay for the content,” in popular parlance—is chiefly being borne by advertising…which, however, pays less and less and demands more and more as customers increasingly find ways to route around it.
“The Verge’s Web Sucks,” by Les Orchard, quickly countered Nilay’s piece, as Jeremy chronicles (“Les Orchard says what we’re all thinking”). Jeremy then points to a half-humorous letter of surrender posted by Vox Media’s developers, who announce their new Vox Media Performance Team in a piece facetiously declaring performance bankruptcy.
A survey of follow-up barbs and exchanges on Twitter concludes Jeremy’s piece (which you must read; do not settle for this sloppy summary). After describing everything that has so far been said, Mr Keith weighs in with his own opinion, and it’s what you might expect from a highly thoughtful, open-source-contributing, standards-flag-flying, creative developer:
I’m hearing an awful lot of false dichotomies here: either you can have a performant website or you have a business model based on advertising. …
Tracking and advertising scripts are today’s equivalent of pop-up windows. …
For such a young, supposedly-innovative industry, I’m often amazed at what people choose to treat as immovable, unchangeable, carved-in-stone issues. Bloated, invasive ad tracking isn’t a law of nature. It’s a choice. We can choose to change.
Me, I’m torn. As a 20-year-exponent of lean web development (yes, I know how pretentious that sounds), I absolutely believe that the web is for everybody, regardless of ability or device. The web’s strength lies precisely in its unique position as the world’s first universal platform. Tim Berners-Lee didn’t invent hypertext, and his (and his creation’s) genius doesn’t lie in the deployment of tags; it subsists in the principle that, developed rightly, content on the web is as accessible to the Nigerian farmer with a feature phone as it is to a wealthy American sporting this year’s device. I absolutely believe this. I’ve fought for it for too many years, alongside too many of you, to think otherwise.
And yet, as a 20-year publisher of independent content (and an advertising professional before that), I am equally certain that content requires funding as much as it demands research, motivation, talent, and nurturing. Somebody has to pay our editors, writers, journalists, designers, developers, and all the other specialtists whose passion and tears go into every chunk of worthwhile web content. Many of you reading this will feel I’m copping out here, so let me explain:
It may indeed be a false dichotomy that “either you can have a performant website or you have a business model based on advertising” but it is also a truth that advertisers demand more and more for their dollar. They want to know what page you read, how long you looked at it, where on the web you went next, and a thousand other invasive things that make thoughtful people everywhere uncomfortable—but are the price we currently pay to access the earth’s largest library.
I don’t like this, and I don’t do it in the magazine I publish, but A List Apart, as a direct consequence, will always lack certain resources to expand its offerings as quickly and richly as we’d like, or to pay staff and contributors at anything approaching the level that Vox Media, by accepting a different tradeoff, has achieved. (Let me also acknowledge ALA’s wonderful sponsors and our longtime partnership with The Deck ad network, lest I seem to speak from an ivory tower. Folks who’ve never had to pay for content cannot lay claim to moral authority on this issue; untested virtue is not, and so on.)
To be clear, Vox Media could not exist if its owners had made the decisions A List Apart made in terms of advertising—and Vox Media’s decisions about advertising are far better, in terms of consumer advocacy and privacy, than those made by most web publishing groups. Also to be clear, I don’t regret A List Apart’s decisions about advertising—they are right for us and our community.
I know and have worked alongside some of the designers, developers, and editors at Vox Media; you’d be proud to work with any of them. I know they are painfully aware of the toll advertising takes on their site’s performance; I know they are also doing some of the best editorial and publishing work currently being performed on the web—which is what happens when great teams from different disciplines get together to push boundaries and create something of value. This super team couldn’t do their super work without salaries, desks, and computers; acquiring those things meant coming to some compromise with the state of web advertising today. (And of course it was the owners, and not the employees, who made the precise compromise to which Vox Media currently adheres.)
Put a gun to my head, and I will take the same position as Jeremy Keith. I’ll even do it without a gun to my head, as my decisions as a publisher probably already make clear. And yet, two equally compelling urgencies in my core being—love of web content, and love of the web’s potential—make me hope that web and editorial teams can work with advertisers going forward, so that one day soon we can have amazing content, brilliantly presented, without the invasive bloat. In the words of another great web developer I know, “Hope is a dangerous currency—but it’s all I’ve got.”
Apple, like Facebook, has entered into a standoff with the publishing industry and the open, if for-profit, web. And it’s being done under the aegis of design: choose a better reading experience on our curated platform, they offer, or let us clean up that pesky advertising on the open web.
⇛ Is the web under threat? Will Facebook or Apple kill or save journalism? Share your thoughts or your favorite links on the subject. Bonus points for older articles.
Material Design: Why the Floating Action Button is bad UX design
I HIGHLIGHTED so many passages in this brief, well-focused design argument, it’s almost embarrassing. Read it (it takes about three minutes), and you’ll wear out your virtual highlighter, too:
Material Design is a design language introduced by Google a year ago, and represents the company’s bold attempt at creating a unified user experience across all devices and platforms. It’s marked with bold colours, a liberal but principled use of shadows to indicate UI layers, and smooth animations that provide a pretty pretty user experience on Android (and some Google apps on iOS).
One thing about Material Design, however, has bugged me ever since it was introduced last year: Floating Action Buttons.
FABs are circular buttons that float above the UI and are “used for a promoted action,” according to Google. They act as call to action buttons, meant to represent the single action users perform the most on that particular screen.
And because of the bold visual style of Material Design, FABs are strikingly hard to ignore and stand out — and herein lies the problem.
While FABs seem to provide good UX in ideal conditions, in actual practice, widespread adoption of FABs might be detrimental to the overall UX of the app. Here are some reasons why.