tech support 8

  • Subscribe to our RSS feed.
  • Twitter
  • StumbleUpon
  • Reddit
  • Facebook
  • Digg

Friday, 13 April 2012

Where's the Viewport Size Data?

Posted on 07:38 by Unknown


Chart of screen resolution from StatCounter.




StatCounter released data on Wednesday showing that the screen resolution of 1,366 x 768 has surpassed 1,024 x 768 as the most common screen resolution. If you've paid attention to the drive for widescreen displays on newer machines, this may not come as much of a surprise to you. I find it more surprising nobody has commented on the decline of most higher resolutions.




What was surprising was this quote in the release:




The screen resolution size people are using is a critical factor for developers when it comes to web design, particularly in the case of fixed width web pages.



For web developers who still develop fixed-width layouts, especially targeting 1,024 x 768, this doesn't matter. Those developers are already lost to us.




For developers who know that screen resolution doesn't necessarily equate to window, and by extension viewport, sizes then this still doesn't matter.




For developers who actually understand the concepts behind responsive web design (RWD) then this doesn't matter.




As anyone in this space knows, that minor shift in numbers that put the wider screen resolution (still the same height) just above the previous champ doesn't require a change to our processes. A skilled developer already has taken the time to assess the audience of a site, or when that data is unknown, is already coding and designing to accommodate various screen resolutions and window sizes. The only real challenge here is protecting our clients from hearing those data points in a vacuum and trying to react. We just need to be smart about counseling them.




That hasn't stopped it from getting a fair amount of attention from the more well-known web folk. Over at .net Magazine (Browser screen resolution stats rile devs) there are some quotes that seem a bit too reactive, along with some that are a fair bit smarter.




If you are somehow caught up with concerns over screen resolutions (and there are some valid reasons to be), then just don't forget that viewport sizes aren't the same as screen resolutions. Scrollbars, button bars, and other browser chrome all take away from that space. Twelve (12!) years ago I wrote a couple of articles addressing that, one of which gathered and presented all the data: Real-World Browser Size Stats, Part II. Last year Chris Coyier wrote a similar article: Screen Resolution ≠ Browser Window. This isn't new stuff.




If you want to take StatCounter to task for anything, then ask them this — where is the viewport size data?

Email ThisBlogThis!Share to XShare to FacebookShare to Pinterest
Posted in browser, design, standards, usability, UX | No comments
Newer Post Older Post Home

0 comments:

Post a Comment

Subscribe to: Post Comments (Atom)

Popular Posts

  • Social Media Day 2011 in Buffalo #smdayBUF
    Last night marked the second Mashable-sponsored Social Media Day here in Buffalo. With 154 RSVPs for the event, the venue, The Eights Bist...
  • Web Accessibility Sorta-Infographic
    WebAIM is a non-profit organization within the Center for Persons with Disabilities at Utah State University. It has a reputation (perhaps o...
  • The Science of Trust in Social Media
    I am one of those people who always needs to see proof of some assertion, evidence to back up a claim. While I can accept anecdotal evidence...
  • Browser Performance Chart
    Jacob Gube has posted a handy chart over at Six Revisions titled " Performance Comparison of Major Web Browsers ." He tests the c...
  • Facebook, HTML5, and Mis-Reporting
    My Twitter stream and the headlines of sites across the web yesterday lit up with Facebook's CEO blaming its stock price (failure to mee...
  • Developer Discusses Dyslexia and Dyscalculia
    Sabrina Dent , a web designer hailing from Ireland, has blogged about her struggle with dyslexia and dyscalculia and web applications today...
  • Now the Mobile Web Is Dead?
    It was barely two years ago that I scoffed when Wired declared the web dead ( Enough about the Death of the Web ). Fast forward to today and...
  • Speaking at Mom 2.0 in Houston, TX
    I will be in Houston this week to speak at the Mom 2.0 Summit (Feb. 18-20, 2010, Houston, TX). To make it a little easier to describe, here...
  • ICANN Moves .org Away from VeriSign
    This Saturday, the .org top-level domain (TLD) will no longer be privately managed. With VeriSign's contract with ICANN for management ...
  • Current CSS3, HTML5 Support
    The Tool Last week saw the launch of FindMeByIp.com , a very handy web site that displays a user's current IP address (along with a geog...

Categories

  • accessibility
  • Adobe
  • analytics
  • Apple
  • apps
  • ARIA
  • Bing
  • Blink
  • Brightkite
  • browser
  • Buzz
  • Chrome
  • clients
  • css
  • design
  • Facebook
  • Firefox
  • Flash
  • fonts
  • food
  • Foursquare
  • g11n
  • geolocation
  • globalization
  • Google
  • Gowalla
  • html
  • i18n
  • ICANN
  • infographic
  • Instagram
  • internationalization
  • internet
  • Internet Explorer
  • JavaScript
  • JAWS
  • Klout
  • L10n
  • law
  • localization
  • Lynx
  • Mapquest
  • Microsoft
  • mobile
  • Netscape
  • ning
  • Opera
  • patents
  • picplz
  • Plus
  • print
  • privacy
  • project management
  • QR
  • rant
  • RSS
  • Safari
  • SCVNGR
  • search
  • SEM
  • SEO
  • social media
  • Sony
  • speaking
  • standards
  • SVG
  • touch
  • translation
  • Twitter
  • typefaces
  • usability
  • UX
  • Verizon
  • video
  • W3C
  • WAI
  • WCAG
  • WebKit
  • whatwg
  • Wired
  • WOFF
  • xhtml
  • Yahoo
  • YouTube

Blog Archive

  • ►  2013 (39)
    • ►  December (1)
    • ►  November (7)
    • ►  September (4)
    • ►  July (3)
    • ►  June (2)
    • ►  May (5)
    • ►  April (3)
    • ►  March (6)
    • ►  February (2)
    • ►  January (6)
  • ▼  2012 (63)
    • ►  December (2)
    • ►  November (4)
    • ►  October (5)
    • ►  September (5)
    • ►  August (4)
    • ►  July (6)
    • ►  June (7)
    • ►  May (7)
    • ▼  April (8)
      • Don't Blame Opera, Blame Devs
      • WHATWG as W3C Community Group in Name Only
      • Dining in the Dark
      • Speaking at Buffalo's Entrepalooza 2012 - May 10
      • Where's the Viewport Size Data?
      • Announcing PrintShame.com
      • More Evidence of the Need for Print Styles
      • W3C CSS Odor Module Released
    • ►  March (5)
    • ►  February (3)
    • ►  January (7)
  • ►  2011 (67)
    • ►  December (5)
    • ►  November (7)
    • ►  October (5)
    • ►  September (4)
    • ►  August (8)
    • ►  July (3)
    • ►  June (8)
    • ►  May (3)
    • ►  April (1)
    • ►  March (6)
    • ►  February (6)
    • ►  January (11)
  • ►  2010 (100)
    • ►  December (8)
    • ►  November (7)
    • ►  October (5)
    • ►  September (10)
    • ►  August (7)
    • ►  July (11)
    • ►  June (12)
    • ►  May (6)
    • ►  April (8)
    • ►  March (10)
    • ►  February (5)
    • ►  January (11)
  • ►  2009 (51)
    • ►  December (9)
    • ►  November (6)
    • ►  October (21)
    • ►  September (13)
    • ►  August (2)
  • ►  2003 (3)
    • ►  October (1)
    • ►  January (2)
  • ►  2002 (9)
    • ►  December (1)
    • ►  June (3)
    • ►  April (1)
    • ►  March (3)
    • ►  January (1)
  • ►  2001 (1)
    • ►  February (1)
  • ►  2000 (4)
    • ►  October (1)
    • ►  July (1)
    • ►  June (1)
    • ►  January (1)
  • ►  1999 (7)
    • ►  November (1)
    • ►  September (2)
    • ►  August (2)
    • ►  July (1)
    • ►  June (1)
Powered by Blogger.

About Me

Unknown
View my complete profile