{"id":24679,"date":"2012-05-01T00:00:00","date_gmt":"2012-05-01T00:00:00","guid":{"rendered":"https:\/\/alienroad.com\/google-bilgi-bankasi\/responsive-design-harnessing-the-power-of-media-queries\/"},"modified":"2012-05-01T00:00:00","modified_gmt":"2012-05-01T00:00:00","slug":"responsive-design-harnessing-the-power-of-media-queries","status":"publish","type":"ar_kb","link":"https:\/\/alienroad.com\/google-bilgi-bankasi\/responsive-design-harnessing-the-power-of-media-queries\/","title":{"rendered":"Responsive design \u2013 harnessing the power of media queries"},"content":{"rendered":"

Tuesday, May 01, 2012<\/p>\n

\n We love data, and spend a lot of time monitoring the analytics on our websites. Any web developer
\n doing the same will have noticed the increase in traffic from mobile devices of late. Over the
\n past year we’ve seen many key sites garner a significant percentage of pageviews from smartphones
\n and tablets. These represent large numbers of visitors, with sophisticated browsers which support
\n the latest HTML, CSS, and JavaScript, but which also have limited screen space with widths as
\n narrow as 320 pixels.\n<\/p>\n

\n Our commitment to
\n accessibility<\/a> means we
\n strive to provide a good browsing experience for all our users. We faced a stark choice between
\n creating mobile specific websites, or adapting existing sites and new launches to render well on
\n both desktop and mobile. Creating two sites would allow us to better target specific hardware, but
\n maintaining a single shared site preserves a canonical URL, avoiding any complicated redirects,
\n and simplifies the sharing of web addresses. With a mind towards maintainability we leant towards
\n using the same pages for both, and started thinking about how we could fulfill the following
\n guidelines:\n<\/p>\n

    \n
  1. Our pages should render legibly at any screen resolution<\/b><\/li>\n
  2. We mark up one set of content, making it viewable on any device<\/b><\/li>\n
  3. We should never show a horizontal scrollbar, whatever the window size<\/b><\/li>\n<\/ol>\n

    \"The<\/p>\n

    Implementation<\/h2>\n

    \n As a starting point, simple, semantic markup gives us pages which are more flexible and easier to
    \n reflow if the layout needs to be changed. By ensuring the stylesheet enables a
    \n     liquid layout<\/a>,
    \n we’re already on the road to mobile-friendliness. Instead of specifying width<\/code> for
    \n container elements, we started using max-width<\/code> instead. In place of
    \n height<\/code> we used min-height<\/code>, so larger fonts or multi-line text don’t
    \n break the container’s boundaries. To prevent fixed width images “propping open” liquid columns,
    \n we apply the following CSS rule:\n<\/p>\n

    <\/div>\n

    \n Liquid layout is a good start, but can lack a certain finesse. Thankfully
    \n     media queries<\/a> are now
    \n     well-supported in modern browsers<\/a>
    \n including IE9+ and most mobile devices. These can make the difference between a site that degrades
    \n well on a mobile browser, vs. one that is enhanced to take advantage of the streamlined UI. But
    \n first we have to take into account how smartphones represent themselves to web servers.\n<\/p>\n

    Viewports<\/h2>\n

    \n When is a pixel not a pixel? When it’s on a smartphone. By default, smartphone browsers pretend to
    \n be high-resolution desktop browsers, and lay out a page as if you were viewing it on a desktop
    \n monitor. This is why you get a tiny-text “overview mode” that’s impossible to read before zooming
    \n in. The
    \n     default viewport width<\/a>
    \n for the default Android browser is 800px, and 980px for iOS, regardless of the number of
    \n     actual physical pixels<\/a>
    \n on the screen.\n<\/p>\n

    \n In order to trigger the browser to render your page at a more readable scale, you need to use the
    \n viewport meta element:\n<\/p>\n

    <\/div>\n

    \n Mobile screen resolutions vary widely, but most modern smartphone browsers currently report a
    \n standard device-width<\/code> in the region of 320px. If your mobile device actually has a
    \n width of 640 physical pixels, then a 320px wide image would be sized to the full width of the
    \n screen, using double the number of pixels in the process. This is also the reason why text looks
    \n so much crisper on the small screen \u2013 double the pixel density as compared to a standard desktop
    \n monitor.\n<\/p>\n

    \n The useful thing about setting the width<\/code> to device-width<\/code> in the viewport
    \n meta<\/code> tag is that it updates when the user changes the orientation of their smartphone or tablet.
    \n Combining this with media queries allows you to tweak the layout as the user rotates their device:\n<\/p>\n

    <\/div>\n

    \n In reality you may find you need to use different breakpoints depending on how your site flows and
    \n looks on various devices. You can also use the orientation<\/code> media query to target
    \n specific orientations without referencing pixel dimensions,
    \n     where supported<\/a>.\n<\/p>\n

    <\/div>\n

    \"The<\/p>\n

    A media queries example<\/h2>\n

    \n We recently re-launched the
    \n     About Google<\/a> page. Apart from
    \n setting up a liquid layout, we added a few media queries to provide an improved experience on
    \n smaller screens, like those on a tablet or smartphone.\n<\/p>\n

    \n Instead of targeting specific device resolutions we went with a relatively broad set of
    \n breakpoints. For a screen resolution wider than 1024 pixels, we render the page as it was
    \n originally designed, according to our 12-column grid. Between 801px and 1024px, you get to see a
    \n slightly squished version thanks to the liquid layout.\n<\/p>\n

    \n Only if the screen resolution drops to 800 pixels will content that’s not considered core content
    \n be sent to the bottom of the page:\n<\/p>\n

    <\/div>\n

    With a final media query we enter smartphone territory:<\/p>\n

    <\/div>\n

    \n At this point, we’re not loading the large image anymore and we stack the content blocks. We also
    \n added additional whitespace between the content items so they are more easily identified as
    \n different sections.\n<\/p>\n

    With these simple measures we made sure the site is usable on a wide range of devices.<\/p>\n

    \"The<\/p>\n

    Conclusion<\/h2>\n

    \n It’s worth bearing in mind that there’s no simple solution to making sites accessible on mobile
    \n devices and narrow viewports. Liquid layouts are a great starting point, but some design
    \n compromises may need to be made. Media queries are a useful way of adding polish for many devices,
    \n but remember that
    \n     25% of visits<\/a> are
    \n made from those desktop browsers that do not currently support the technique and there are some
    \n     performance implications<\/a>.
    \n And if you have a fancy widget on your site, it might work beautifully with a mouse, but not so
    \n great on a touch device where fine control is more difficult.\n<\/p>\n

    \n The key is to test early and test often. Any time spent surfing your own sites with a smartphone
    \n or tablet will prove invaluable. When you can’t test on real devices, use the
    \n     Android SDK<\/a> v\u0259 ya
    \n     iOS Simulator<\/a>.
    \n Ask friends and colleagues to view your sites on their devices, and watch how they interact too.\n<\/p>\n

    \n Mobile browsers are a great source of new traffic, and learning how best to support them is an
    \n exciting new area of professional development.\n<\/p>\n

    Some more examples of responsive design at Google:<\/p>\n