nemetral.net | Insightful posts on design and code

April 27, 2008 · Category design · icon0

Google’s unbreakable design

This article was written by nemetral.

Voices matter! Please feel free to share your opinion, ask for more explanations or point out divergences using comments.

No time to read this now? Bookmark it and come back later..

Note: this post is a down-to-earth trackback to the Official Google’s Blog latest post about “What makes a design Googley?”.

In a more basic way than the much abstract principles explained in the aforementioned article, here are five principles that, to my view, can sum up pretty well a “Googley design” as we can experience it for years:

  1. use Arial, no matter what
  2. keep the default blue for hyperlinks (and don’t remove the underline)
  3. go for rounded corners, definitely
  4. leave a lot of white space
  5. do not style form buttons

In a word: raw design. Now I don’t say this design is awful. Voices have already contested Google’s design style (and some folks out there have even redacted comprehensive proposals to revamp Google’s search interface) but I won’t. On the contrary, Google’s design principles used to give me two sensations/expectations in terms of UX (user experience):

  1. there’s such an impressive server-side engine underhood delivering basic this html design
  2. apps are in perpetual beta.. and one day maybe the design will be consolidated among them

Time went by and the design consolidation I was expecting didn’t really happen (look at Yahoo! homepage and you’ll have an idea of what I was naively expecting for Google’s). Of course, it is now possible to switch from one Google App to the other with the top-bar, but that’s still not what I’d call a consolidated design.

After all these years, the user experience I now have when using Google apps is threefold:

  1. still this feeling of power coming from a top-notch server-side architecture
  2. extreme decoupling between Google’s applications (as if the unconsolidated design ruled the apps server-side background)
  3. raw but unbreakable design

And believe me, the last one is perhaps the most important. If Google’s design is that raw, it’s not because they lack designers (they even hire the best ones), it must be a voluntary decision. A marketing decision? Maybe. I don’t mean to dive again in the polemic after Soble published his famous post on anti-marketing design, but yes I think Google’s raw design looks unbreakable, more or less consciously, gives the user the feeling that its server-side technology is unbreakable as well.

Entries (RSS) Did you enjoy this post? Consider subscribing to the RSS feed!

Leave a comment