One size never fits all

1 minute read

While it is nice that new smartphones can render virtually any website reasonably well, we are remiss to not take context into account. Is “reasonably well” really your end goal? I have been dipping my toe into making this site more optimized for mobile consumption by serving up some size delineated styles. I wanted to share a couple of notes on my approach.

Early on, I was seduced by the siren’s call of tools that offered a “native experience”. Frameworks like iWebkit and jQTouch promised to make my website look less like my website and more like a native iPhone app. At first, this seemed awesome. Doubly so, considering how easy either tool was to leverage via the the way drupal handles multisite installs. Under closer consideration, however, I found two big issues with this approach. First, I didn’t want my site to look like a generic app… I wanted it to look like my site. Secondly, looking like a generic iPhone app on an Android phone seems even less optimal. Don’t get me wrong, these frameworks are super impressive… as long as what you’re trying to do is create a usable interface with minimal effort. Most websites are, at least to some extent, about marketing. Blending in is not the first priority.

Enter media queries. Overriding some of the layout and letting most of the style persist seems to be the path of least resistance. We need to regard webkit based mobile browsers more as damage control for users than a crutch for creators. Mobile isn’t the future anymore… it has been the present for quite some time.