Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The primary reason is that people want more and more people to access their website. Almost 10 years ago, 1024x768 was the most common display resolution. After that while new and higher resolution displays have come in, there has not been a significant jump in the vertical resolution (768) of low end devices. Even now (beginning of 2012) almost 50% displays use max 800p as the vertical resolution. </p> <p>So 1024x768 is a standard minimum resolution for which people design websites. There are high chances that if you design for wider/bigger resolutions, people using these devices may not see them on the top of their screen (without scrolling) and the content may remain unnoticed.</p> <p>Check this wikipedia link for more detailed stats <a href="http://en.wikipedia.org/wiki/Display_resolution" rel="nofollow">http://en.wikipedia.org/wiki/Display_resolution</a></p> <p>To answer the other question, why not have multiple versions? Two reasons mainly:</p> <ol> <li>Many websites actually are dynamically scalable. Check facebook or google images for example. Depending on your screen resolution they use the extra area to fit in extra content. This strategy generally suits websites that have blocks of content that can be fit in dynamically. </li> <li>There are studies that suggest that for optimal and quick reading around 6-7 words or 500px (not exact numbers) is the best width. Anything more than that causes too much horizontal span and decreases reading speed. This affects the resolution of websites that are more about text for e.g. blogs and news websites.</li> </ol>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload