Guymon

In recent years, I’ve been meeting with more companies that request “an iPhone website” as part of their project. It’s an interesting phrase: At face value, of course, it speaks to mobile WebKit’s quality as a browser, as well as a powerful business case for thinking beyond the desktop. But as designers, I think we often take comfort in such explicit requirements, as they allow us to compartmentalize the problems before us. We can quarantine the mobile experience on separate subdomains, spaces distinct and separate from “the non-iPhone website.” But what’s next? An iPad website? An N90 website? Can we really continue to commit to supporting each new user agent with its own bespoke experience? At some point, this starts to feel like a zero sum game. But how can we—and our designs—adapt?

Google Browser Size is a visualization of browser window sizes for people who visit Google. For example, the “90%” contour means that 90% of people visiting Google have their browser window open to at least this size or larger.
This is useful for ensuring that important parts of a page’s user interface are visible by a wide audience.

Usually the first thing that comes to a designer’s mind when designing a website for a Content Management System (CMS) like Drupal is the “boring square style.” It can be challenging to have an out-of-the-box design that is still flexible enough to be scalable, but it is possible. You might say that in order to be truly creative a designer needs some rules to break, and the tight boundaries that can come with designing for a CMS can offer new challenges. This is why designing for Drupal is anything but boring – it can be interesting and challenging for any designer.