Tag Info

Hot answers tagged

3

The key thing is to retain 100% of the sites meaning while reducing the size of the screen. The device used to browse your site should not dictate the contained meaning. For text this means that it isn't ever removed. Even if it is hidden (think of a menu put into a hamburger for example) it should still exist in an accessible way in the HTML, either for a ...


2

Scrolling isn't necessarily a bad thing. In fact people read text on a scrolling page faster than multi-page document. If you only have 13 items on the list, this is only like 2 screen height of scrolling, a lot of mobile pages out there are way lengthier. I wouldn't be terribly concern on that front. 13 items are quite a lot for somebody to take in at once ...


2

An animation when opening the menu probably likely won't negatively affect the usability much (the user still knows where to click the menu and expects a menu to open). An animation does add some "delight" to the experience because it makes the transition visually smooth and it helps the user follow along with what they selected. That said, if you are ...


2

I'd first question whether you need global navigation on mobile. I'm often asked to implement global navigation on projects because project leads have a belief that users want to 'hand out' in the application and be able to navigate from one point to any other point. But in terms of actual usage, that's not now most people interact with most ...


1

Nice question. I think there is no "best practice" here because it really depends on what your wireframing objectives are (e.g. high fidelity vs low fidelity, proof of concept vs specific interaction design, etc). But if it helps, here is how I wireframe responsive websites: I use wireframes for very rapid, iterative UX design. So speed and iterability ...


1

Your breakpoints should be defined by your content and your content only. Take each element case by case and decide based on ease of content consumption at what point it should break into some other layout configuration. It's a mistake to silo everything on a site into predetermined screen widths as you'll end up individual elements which are little bit ...


1

The hamburger menu... I'm torn. The hamburger menu decreases discoverability because it hides what the user is more than likely going to use to... well... discover At a glance, the user can tell what's where and how to find what they are looking for. Being hidden underneath someplace isn't ideal for scanability. Having said that, stay away from keeping it ...


1

Responsive = alter for context A proper responsive design (one that has endured a rigorous UX process) manipulates page content based on a user's anticipated context. That's difficult to evaluate because you can no longer just do device detection (too many!) so you lean on viewport as an indicator. But you can tell a lot from that number. Whether you ...


1

To stay in scope I'm going to assume that you must use a tabular form (i.e. decomposing the data into cards, lists, or subviews is not an option). Tables will never really be fully responsive friendly, but that doesn't mean they shouldn't be used at all. Sometimes it's a design constraint you have to work with and so it's not helpful to say "don't use ...


1

Create focus The trouble with tables is that there's no focus. No hierarchy. Just a whole bunch of data to be crunched. They have their place, but the use cases are nowhere near as numerous as their usage. Cards The dominant pattern to solve this today has it's very own buzz word: "cards". There's nothing new about the pattern, but it works well in a ...



Only top voted, non community-wiki answers of a minimum length are eligible