As a web developer, over the years I’ve asked the producers/project managers I’ve worked with “and what browsers are we supporting?” more than once, for every project I have worked on as though its fine to think there are some browsers we just don’t support. We understood that the internet is accessed by a wide range of browsers, it should be accessible and inclusive and project’s content should be viewable for as many people as possible. But, we have a limited about of time and resources and there was only so much graceful degradation and progressive enhancement we could do.
When AREA 17 first designed Quartz in 2012, our client at The Atlantic was forward thinking in their brief: ignore desktop. A simple, yet revolutionary statement.
By ignoring the desktop context, we had the freedom to serve the mobile context. We killed the homepage, dropped the right column, inserted premium native ads and reduced the navigation and branding. Context is a primary consideration when designing a user interface. This is understood by most UI designers and as mobile asserts its dominance, many of us adhere to a mobile-first approach.
The Pixel School is a design methodology created by Arnaud Mercier (May 10, 1972 – September 26, 2011) and formalized by AREA 17. It is a defined way of working that has great impact on the final product. It consists of a set of design principles and the techniques to achieve them.
Disenchanted with the quality of design on the web, Arnaud created the Pixel School in 1999. It became a cornerstone of his design process and the predominant characteristic of his influential body of work. In 2005, Arnaud established the Pixel School as AREA 17’s design methodology. Later, it was formalized in collaboration with Kemp Attwood, David Lamothe and Martin Rettenbacher.
The Pixel School is a living document, updated as we refine our design approach and process. It is part of a series of guides that define how we do things as an agency. While all other guides are private, we have made the Pixel School available to the public.
We like logos – making them, looking at them and taking them on long walks on sunny afternoons in the park. Please don’t laugh, it’s unkind.
The process of exploring a symbol for someone or something presents so much potential. The road is clear, the sky is blue and the options are many. Creativity abounds, imagination runs wild and our electrons and neurons bounce around in an ever changing free-for-all that would make quantum theorists proud.
And then, the dreaded day comes, the selection process. One by one, the mark flecked, the seal splotched, the stamp smeared, the emblem blotched. One by one specked, stained and smudged until the one—that one—stands out.
If you haven’t played around with Wildcard yet, you should definitely check it out. The news and entertainment app for iOS and Android provides additional context to curated top stories by collecting articles from multiple sources and splicing them with summaries of key milestones as the story develops. Beautifully designed and high-performing, one of the most pleasing aspects of the app are its subtle use of tactility and animation. The other day the app prompted me to press and hold a card for additional options — sure enough, that gesture introduces a modal view where users can quickly share and save the article for later without the investment of loading the card itself.
As digital product engineers, there are a few over-riding principles that govern our work. As an agency, one of the most critical of these is “build once, use many times.” Using existing building blocks for standard features allows us to develop rapidly while leaving budget for the innovative features that will actually differentiate our clients’ product.
In many cases, these building blocks are part of our own arsenal of code, standardized for reuse. In other cases, we evaluate 3rd party services that allow us to introduce production-ready features without the expense of developing and maintaining them.
If you’ve ever worked in publishing you know designers loathe ads because they tend to force web sites into banal, homogenous layouts based on a few arbitrary but standardized ad sizes. Much worse, however, ads tend to be distractingly ugly and, in a digital world, they literally get in the way of the content. We’re forced to overlook this offense to aesthetic purity and a zen reading experience, of course, because advertising is generally what pays our salaries.
Redesigns of large scale editorial platforms and publisher websites have been popping up like wild flowers lately. ESPN (led by AREA 17), Bloomberg, The Guardian, The Wall Street Journal, The Atlantic, CNN, and The National Review have all launched new sites in the past several months. Considering our (AREA 17) long-standing interest and deep experience in the editorial world it seems worthwhile to note the interesting aspects of some of the new wave of designs.
“[Web] Performance is a lot like plumbing. It’s hard to get people to pay attention to it until something is wrong.” — Tim Kadlec
Performance is an often invisible part of our online experience. As Tim Kadlec notes, most people don’t notice it until something’s wrong. Performance is, in fact, the cornerstone of any successful user experience.
We’ve written before about our soft spot for print, and in particular, brands that succeed at creating original content. There’s a fantastic article on this topic in Eye no. 88 that looks behind the scenes at the designers, content creators and making of Pegasus, a premium magazine that was funded by Mobil from 1970 to 1985.
I don’t think any company was producing anything like this,” says [editor Gregory] Vitiello, “so tangential to the business and intended to be so thought-provoking.
Read Powered Flight.
AREA 17 operates primarily out of studios in New York and Paris. But we also have satellite offices in several other parts of the world. At times there can be a nine hour time differential between staff members. Thankfully email, Hipchat, Google Hangouts, Skype, and a few years of practice means this isn’t much of a problem for us. However, I sometimes still have problems with doing the mental arithmetic necessary to calculate what time it is for everyone everywhere else—especially when organising meetings. To try and alleviate this, I built a web app over the holidays that displays all of the primary timezones in which AREA 17 operates so with quick glance you can see what time it is in those places.
2014 was a big year at AREA 17. We had the opportunity to work with some amazing new clients, develop deeper partnerships with existing ones, have our voices heard from coast to coast (and country to country), soak up some California sun, and come back home again to expanding studios in Paris and New York. We wished a few old friends the best in new adventures and welcomed a cadre of talented new colleagues hailing from as far away as Dubai and Detroit and as close as Long Island and Brooklyn Heights.
On a recent static style guide build I got tired of manually inserting sample code content into
<code> tags; especially as I hadn’t fully made up my mind on exactly what the markup should be. Each change meant I was copy and pasting the new markup into a new window in my text editor and search and replacing the < and > so that it would render as expected in the browser. I see most problems as a Front End problem so I wrote a quick function to do this for me. I’m writing this down and sharing because a quick Google search didn’t reveal any similar functions.
I recently came across an interesting article by Simon Owens on the Nieman Lab’s site called “It’s small touches that can make a difference in New York’s layouts.” The piece starts with a simple observation:
For years we were using Compass with Sass with our product, Krrb, to make our lives (mine at least) a bit easier:
- no browser prefixes to take care off
- cool shortcuts
- easy image sprites generation
However, there were still performance issues.
Compass is huge and take lots of time to compile—from five to eight seconds for each deploy. So I decided to get rid of it completely.
Who invests in you matters more than how much they invest in you. As Paul Rand often said, the quality of the client will determine the quality of the design. If you get money from the wrong people you will be negatively constrained, so choose well.
John Maeda’s move from President of the Rhode Island School of Design to the venture capital firm KPCB last year is as clear a sign as any of the increasing value placed on design in business. This topic, which has been covered extensively over the last few years (I offered my own take this past summer), is presented in a refreshingly personal monthly newsletter by Maeda that arrived in my inbox today, including the above quote.
The newsletter, a companion to Maeda’s twitter stream @designandvc, shares his thought-provoking and valuable observations that tend to stay with me long after I’ve read them. I would also suggest reading Maeda’s article for the Wall Street Journal, “Three Principles for Using Design Successfully“ as well as the Design and VC blog post where he’s collected an archive of articles on the subject, going back to 2004. I look forward to more from Maeda as he continues to champion the role of design and designers from his new post in Silicon Valley.
I recently spent a week in Vancouver, where the seeds of my AREA 17 adventure were planted. It was there I met Arnaud Mercier in Y2k while working for Blast Radius and I still remember the buzz that was created when his Elixir Studio Subway portfolio got sent around, along with the news that he would soon be joining our ranks. I was only a couple of weeks into my first real position as a designer, and over the next couple of years I had the opportunity to learn from him and a host of other incredibly talented art directors whom I continue to hold in high regard. I guess that’s why Vancouver has always felt particularly rich in design for me, despite the fact that the Canadian city does not have as many cultural offerings as New York or Paris (a fact subtly lamented by Arnaud at the time). So it was with an odd sense of pride that I discovered a thriving design culture, especially in Gastown, the city’s oldest neighborhood.
In 1992 the Olympic Games were held in Barcelona. Since then, the local design scene has grown immensely, so much so that Barcelona now has more design schools than any other metropolitan region in Europe. The city is now recognized globally as a forward thinking design city with the branding to prove it.
In order to maintain Barcelona’s recent reign of design dominance the city’s local government, public and private institutions, and companies have made big efforts to create and build the Barcelona brand.
But how exactly do you brand a city?
Implementing an analytics tool for analyzing site traffic and basic user behavior is pretty easy these days. For most people Google Analytics will work just fine — it’s free, it has a great interface, and it’s trivial to implement.
At Krrb our needs are slightly more complex. While Google Analytics supports the majority of our traffic analysis, it doesn’t give us everything we need.
Before joining AREA 17 two years ago I spent a year and a half trying to get my startup, justmap.it, off the ground. I wanted to create a simple app where people could log and share places. And while it’s been a grind, I’ve pushed forward and will be releasing a new, much more polished version soon. Maps and places continue to intrigue me and seem to always find a way into all of my work.
The language of interactive design is still in its infancy and frequently draws parallels from its more established counterparts in architecture and the Fine Arts. These creative disciplines do share many similarities and often warrant a dialogue that isn’t mutually exclusive. However as design becomes more ubiquitous in every aspect of our lives, and informs decisions in boardrooms around the world, it’s worth reconsidering how we talk about it. One approach is by embracing simplicity and harnessing the virtues of unpredictability.