GET READY for Lara Hogan, author of Designing For Performance, as she shares pretty much about everything you’ll need to know to design optimally performant front-end web experiences. It’s one of twelve essential sessions that make An Event Apart Austin 2015 the Southwest’s don’t-miss web design and development event of 2015.
IN “HOW DROPBOX Remains Relevant,” Khoi Vinh explains why Dropbox owes much of its success to subtly faceted, user-focused design:
Even in an age when the biggest operating systems in the world actively eschew file hierarchies, Dropbox is thriving—its service matters deeply to countless users. Why? In part it’s because the company works hard at making file hierarchies useful, that they focus on the outcomes of file management and not just on the files and folders.
Absolutely. Dropbox sweats the user experience details as commendably as it masters the considerable engineering challenges required to reliably sync files everywhere a user may need them.
But there’s another reason Dropbox succeeds. And it isn’t despite its emphasis on old-fashioned file hierarchies. It’s because of that emphasis.
⇛ ALTHOUGH Khoi may well be right that “smart passive management of design assets and working files seems inevitable,” I, for one, do not look forward to the day I no longer have direct access to my files and the ability to control where and how they are stored. To my way of thinking, passive management of file assets is okay for screwing around with iPads, where we’re mainly watching TV on Netflix or obsessive-compulsively checking the popularity of our Instagram uploads. But for real work, and even for passionate hobby work (like managing family photos), give me files and folders any day.
Stay with photos a moment. Consider snapshots. For my money, apps like Photos (and, formerly, iPhoto) that “save” me from the “inconvenience” of knowing where my images are do me no favors. Thanks, but no thanks. Let me save photos where I want to save them, not where the system thinks I should save them—typically on a laptop’s rapidly filling solid state hard drive with minimal storage capacity.
Dropbox, with its emphasis on good old-fashioned hierarchies, is superb at automatically saving one original of each photo I take, whether shot with a phone or a fancy camera. No loops, no duplicates, no confusion. In contrast, Photo’s cloud sync options, designed to spare the user the trouble of thinking, always trip me up. Like when, after syncing my phone to my home desktop computer, I tell Photos to delete the photos I’ve just sync’d from my phone. Photos obeys my command, and then instantly restores the photos to my phone from the “cloud.”
Why would a system expect a user who has deleted files to want those files restored a moment later? In what universe of scenarios can that possibly be what the user expects? [Your system may work differently from mine. Your deletes may stick. If so, good on you. You may have checked a different box in a hidden drawer of a preferences dialog, possibly in the app preferences you can set in the app itself, or possibly in the app preferences you set in the phone’s Settings app, or possibly online—say, in iCloud, or possibly in the iCloud settings in the phone’s Settings app. This is simplicity?]
Because my phone and iCloud restore photos as soon as they’re deleted, my Camera Roll is an unwieldly monster—despite my applying common sense, logic, years of design and computer using experience, and hours of conversation with a rapidly dwindling circle of friends—not to mention the hours I’ve spent scouring the web for hints. The whole situation reminds me of an article I saw on the cover of PC World years ago: “Plug ‘n Play: How To Make It Work.” (Hint: If you have to learn how to make it work, it ain’t plug ‘n play. And that’s kind of how I feel about the current state of passive file management.)
⇛ SYSTEMS designed to relieve you of thinking too often end up forcing you to think, and think, and think, without ever solving the problems their supposed simplicity has created for you. How much easier would photo maintenance on my phone be if Photos, like Dropbox, used file hierarchies? I could solve the problem myself in a second, with the click of a checkbox, if only Apple weren’t committed to chasing a future where nobody needs to know anything about how their computer works—and, as a result, some of us have no clue what to do when the computer doesn’t work quite right.
⇛ I UNDERSTAND that these are difficult problems to solve, and that confusion and frustration are the price consumers pay for innovation that may benefit them in the long run, once all the kinks are out. I’m not anti-innovation or anti-Apple.
But I’m a web person. I like files. I like editing a CSS file without necessarily having to edit an HTML file. I like fixing a problem by replacing a corrupted file with a clean one. Maybe I’m set in my ways, but I don’t consider it a hardship to open a folder or replace a file. I wouldn’t be quite as happy with a web where I didn’t “need” to “bother” writing CSS.
In the same way, I like deciding where files go—saving an image for Project A in a Project A folder, a text document for Project B in a Project B folder (and all of it in Dropbox). I’m glad Adobe Lightroom maintains a picture of my photo folder hierarchy in a sidebar of its interface, enabling me to see where my files live, and instantly choose a group of photos by date (instead of, say, scrolling through thousands of files visually). When it’s time to get dressed in the morning, I don’t throw myself into a giant room full of clothes. I pull socks from my sock drawer and shirts from my shirt drawer. I’ve been doing this since I was five years old. It’s not a challenge.
Khoi ends his excellent Dropbox piece thusly:
Maybe we’re all just set in our ways, but people seem at least resigned, and more likely just plain comfortable with managing their files. It may not be what future workflows are built around, but for working designers, the future is hypothetical, and Dropbox works today.
To which I say Amen. And add the hope that, so long as my career lasts, I can keep using a workflow I find easy and comprehensible.
“Don’t make me think.” Absolutely. But, equally, don’t treat me like an idiot. Folders über alles.
Remember: the future will come whether you design for it or not. If your company charges $300,000 for a website that won’t work on next week’s most popular device, your company won’t be able to stay competitive in this business. It might not even be able to stay in the business, period. After all, clients who pay for sites that break too soon will look elsewhere next time—leaving your company perpetually hunting for new clients in a downward spiral of narrowing margins and diminishing expectations.
Your company’s survival is tied to the ability of the products it makes to work in situations you haven’t imagined, and on devices that don’t yet exist. This has alwaysbeen the challenge of web design. It’s one A List Apart has taken seriously since we began publishing, and our archives are filled with advice and ideas you can boil down and present to your bosses.
Source: No Good Can Come of Bad Code
The pace of change in our industry is relentless. New frameworks, processes, and technologies are popping up daily. If you’re feeling overwhelmed, you are not alone. Let’s take a step back and look at the over-arching trajectory of web design. Instead of focusing all our attention on the real-time web, let’s see which design principles and development approaches have stood the test of the time. Those who cannot remember the past are condemned to repeat it, but those who can learn from the past will create a future-friendly web.
UNEXAMINED PRIVILEGE is the real source of cruelty in Facebook’s “Your Year in Review”—a feature conceived and designed by a group to whom nothing terrible has happened yet. A brilliant upper-middle-class student at an elite university conceived Facebook, and college students, as everyone knows, were its founding user group. The company hires recent graduates of expensive and exclusive design programs and pays them several times the going rate to brainstorm and execute exciting new features.
I’m not saying that these brilliant young designers are heartless, or that individuals among them haven’t personally experienced tragedy—that would be mathematically impossible. I have taught some of these designers, and worked with others. Those I’ve known are wonderful people who want to make a difference in the world. And in theory (and sometimes in practice) a platform like Facebook lets them do that.1
But when you put together teams of largely homogenous people of the same class and background, and pay them a lot of money, and when most of those people are under 30, it stands to reason that when someone in the room says, “Let’s do ‘your year in review, and front-load it with visuals,’” most folks in the room will imagine photos of skiing trips, parties, and awards shows—not photos of dead spouses, parents, and children.
So it comes back to this. When we talk about the need for diversity in tech, we’re not doing it because we like quota systems. Diverse backgrounds produce differing points of view. And those differences are needed if we are to put the flowering of internet genius to use actually helping humanity with its many terrifying and seemingly intractable problems.
If we keep throwing only young, mostly white, mostly upper middle class people at the engine that makes our digital world go, we’ll keep getting camera and reminder and hookup apps—things that make an already privileged life even smoother—and we’ll keep producing features that sound like a good idea to everyone in the room, until they unexpectedly stab someone in the heart.
1 Of course, not all my former students and employees work at Facebook; most don’t. But those who have gone there had other, equally lucrative options; they took the job to make Facebook, and maybe the world, a little better.
ON THIS year’s Blue Beanie Day, as we celebrate web standards, we also celebrate our community’s remarkable diversity—and pledge to keep things moving in a positive, humanist direction.
Racism, sexism, misogyny and other forms of foolish, wrongful pre-judging have no place in our beautiful community. As hard as we work to make sure our websites work for everyone, let’s work twice as hard to be certain we are just as open-hearted and welcoming to our peers as our designs are to our users.
AN EVENT APART Chicago—a photo set on Flickr. Pictures of the city and the conference for people who make websites.
Notes from An Event Apart Chicago 2013—Luke Wroblewski’s note-taking is legendary. Here are his notes on seven of the ten presentations at this year’s An Event Apart Chicago.
#aeachi—conference comments on Twitter.
Chicago (Foursquare)—some of my favorite places in the city.
An Event Apart Chicago—sessions, schedule, and speaker bios for the conference that just ended.
AEA Chicago 2013 on Lanyrd—three days of design, code, and content on the social sharing platform for conferences.
A handful of seats are available for the final event of the year, An Event Apart San Francisco at the Palace Hotel, December 9–11, 2013. Be there or be square.
THERE IS ALWAYS more to the story than what we are told. I am not omniscient. It is better to light a single candle than to join a lynch mob. Other people’s behavior is not my business. Truth is hard, epigrams are easy. Anything worth saying takes more than 140 characters. Blogging’s not dead. F____ the 140 character morality police.
THIS MORNING Contents Magazine launched the beginning of something both good and important: a set of guidelines that could lead to a safer world for user-created content.
Contents believes (and I agree) that products and services which make a business of our stuff—the photos, posts, and comments that we share on their platforms—need to treat our content like it matters. Not like junk that can be flushed the moment a product or service gets acquired or goes under.
On the web, popularity waxes and wanes; beloved services come and go. AOL was once mighty. MySpace was unstoppable. Nobody expected Geocities, Delicious, or Gowalla to just disappear, taking our stories, photos, and memories with them. But that’s what happens on the web. Tomorrow it could be Facebook, Twitter, Instagram, or Flickr. We can continue to blindly trust these companies with our family histories, and continue to mourn when they disappear, taking our data with them. Or we can demand something better.
Contents and its small team of advisors have devised three simple rules customer-content-driven services and apps should follow to respect and protect our content:
- Treat our data like it matters. Keep it secure and protect our privacy, of course—but also maintain serious backups and respect our choice to delete any information we’ve contributed.
- No upload without download. Build in export capabilities from day one.
- If you close a system, support data rescue. Provide one financial quarter’s notice between announcing the shutdown and destroying any user-contributed content, public or private, and offer data export during this period. And beyond that three months? Make user-contributed content available for media-cost purchase for one year after shutdown.
You may see this as a pipe dream. Why should a big, successful company like Facebook listen to us? But citizen movements have accomplished plenty in the past, from bringing web standards to our web browsers, to peacefully overthrowing unpopular governments.
I’m on board with the new Contents guidelines and I hope you will be, too. If enough of us raise enough of a sustained fuss over a sufficient period, things will change.