We’re going to geek out a bit today over a few user experience (UX) items that are going to have a substantial impact over not just online design but print design as both formats as users increasingly gravitate toward uniformity. The driving force behind many of these changes is the rise of mobile platform usage; i.e. Smartphones and tablets.
Due to the touch interfaces found on mobile devices, it should come as no surprise that user interface designs attempt to be as finger-friendly as possible. And with users spending more and more time on these devices, they are transferring those interface expectations to their traditional desktop and laptop browser experiences.
Fortunately, traditional web design is embracing these user defined expectations and moving at breakneck speed toward designs that adjust to fit whether accessed via traditional or mobile platform. The result is called Responsive Web Design; an approach that suggests that design and development should respond to the user’s behavior and environment based on screen size, platform, orientation, etc.
In order for responsive designs to work, they need to incorporate as many similar user interface elements as possible that scale from one platform to the other without loss of functionality.
In English, that means a button that might be easy to click with the fine-point tip of a mouse cursor becomes frustratingly fumblerific when used on a touchscreen mobile device.
Responsive design steps in to solve these problems by incorporating standards that scale nicely between all platforms. Two primary areas where this comes into play is font size and button widths (as an aside: a fun related conversation we’ll leave for another date is how Responsive design combined with improved optimization is going to all but eliminate the need for most performing arts groups to shell out big bucks for platform specific app designs).
Font Size
Traditionally, most folks are used to working with a standard body font size from 10px-12px and headline font size from 16px-18px. But what if I said you were going to bump those up to 16px for body font and 28px (on up) for headlines? I can almost hear the responses now.
“Good God man; I’m an adult, not a six year old! Do you want me to start using those telephone poles masquerading as kindergarten pencils as well?”
What if I told you those were exactly the font sizes you were reading right now?
Several months ago, I started ramping up Adaptistration’s font sizes every few weeks until reaching the goal of 16px body font size and 32px (bold) headline size at the beginning of December, 2011. Hopefully, you didn’t really notice since the goal was not to dump it on you all at once.
But take a look at how much of a difference is makes going from smaller font sizes to larger, cross-platform friendly sizes. The following image compares identical homepage content from this blog in the smaller and larger font sizes. For the full impact, make sure you click the expand image icon in the top, left hand corner of the image once it pops up:

Larger (Responsive Web Design friendly) font sizes on top, smaller (traditional) font sizes on bottom – click to enlarge.
[sws_divider_small_padding]
Android User Interface Guidelines[sws_divider_small_padding]
Windows Phone UI Design and Interaction Guide - pdf file[sws_divider_padding]
In the end, the increase in font sizes has certainly had a positive impact on mobile browser average time per page here at Adaptistration. Since putting the final changes in place last December, the page length times have increased nearly 20 percent and since average time per page via regular browser usage only increased by seven percent in the same period, the mobile increase wasn’t likely due to content.
And when it comes to performing organization arts website, increased average time per page means increased sales and donations!








[...] Instead of thinking about platform specific design as a given, rely on solutions that embrace responsive design standards.There will always be edge cases when separate, mobile-specific websites will be a better [...]
[...] covered the topic in much greater detail in recent articles (here, here, here, and here) but all in all, the upgrade was comparatively painless for as many changes [...]