Tag Info

Other than the answer provided by @icc97, a fixed navbar allows users to quickly switch to another page without having to scroll all the way up. This is only exceptionally useful when your page contents may be lengthy (e.g. infinity scroll, blogs or articles) and your users browse through many pages on your site. Facebook, Mashable, ReadWrite and ...

Three big issues when you're considering how to deal with content on mobile devices, especially if you're trying to figure out how to re-prioritize content for different screen sizes or device capabilities. I've been calling this adaptive content, as a partner to adaptive design or responsive design. How is the content written? Truncation might work... if ...

For the most part the pros/cons of this come back to the classic Adaptive vs Adaptable interface argument, where Adaptive interfaces automatically adjust based on user interaction, and adaptable interfaces allow users to manually tweak them. A problem with this in particular is that text size is an accessibility issue. Not everyone has the same eyes, so ...

Below are the sizes I like to design for; not all of these may be ideal for your needs, however I find this tend to provide the cater to the most common configurations of devices out there. When I refer to device width, it is in "device independent pixels" :P 1024px This is the typical device width of 1:1 scale tablet in landscape mode, which also lends ...

In her presentation at An Event Apart in Washington DC 2011 Karen McGrane discussed the need for structured content in Web sites. Following this there were lots of amusing tweets and retweets on twitter of the form: Luke Wrobleski wrote up some notes on her talk in which he says: This is not a technology problem. It’s a strategy problem. Amongst ...

Not an answer, but I want to point out some of the downsides to the fixed header (if a non-answer like this is out of line please let me know). The fixed header is somewhat problematic on devices (Safari iPad and Chrome iPad): when you zoom a section of the page the header can become unfixed or semi-fixed. It will scroll but at a different rate than the ...

As a tech demo it suggests many benefits. Most of the answers here seem to be concentrating on the negative impacts of what happens when you bring the device closer to yourself, thereby decreasing the fontsize, but I believe the benefits of this system are when you come at it from the other direction - how to present content to users viewing it where their ...

I think this kind of thing creates more problems than it solves. On web UIs I assume the user has set the browser font size to a comfortable size for general reading. I use the user set font for the bulk of the text content, i.e. the main reading font. Other font sizes used on the site are derived from the user set font (that is set with units of *em*s or ...

I think that this may have more to do with the sizing of the whole page. As screens get larger, so does the content. And that means more scrolling. If you increase the width of the page content, you would generally also increase the height and this will create more scrolling when the user tries to click a navigation link. Two of your examples (Mashable ...

I design for 320px wide and up. You shouldn't design for a specific set of device sizes because the range of sizes is continuously increasing - a comprehensive list of device sizes isn't comprehensive for very long. The current trend is to design breakpoints with concern for content, not device widths, and I think this approach will work well going ...

Firstly, I just want to say that adaptive and responsive web design are two different things. Adaptive design is essentially responsive design without a fluid grid/images. At my shop, when we build responsive sites, we build the wireframes in HTML/CSS/JS with the actual breakpoints, then move onto visual mock-ups (6-10 JPGs for review: two pages of the ...

One approach is to build a complete set of wireframes using the "default" - or most highly-trafficked - screen size, then show representative examples in the other screen sizes you have designed for. If you have a few common screen patterns, you can probably get away with showing an example (or two) of each pattern. For any interesting one-off screens, ...