Tag Info

Hot answers tagged

48

A web application should always strive to be compatible with the browser's back button. That is, using the back button should have deterministic results within that application that match expected behavior (global consistency). A common scenario that comes to mind with this is an eCommerce site that has a list of products. A user clicks on one of the ...


25

Yes. You should rely on the browser back button. Users expect the button to be there, so make sure it's functional. But should you mimic the same button with its functionality? If your application or website needs it, yes, but not always exactly the same. In some cases, like your example of a webshop, a button that just says back or an arrow might not be ...


7

There are three reasons for this behaviour: A lot of new web apps are utilising Javascript MVC frameworks and the concept of the single page app. In this context, in order tot make the sort of behaviour described work you need to use the history API. This is all very new technology and designers, developers and product managers are still getting to grips ...


7

Rely is the wrong word You're asking if you should rely on the button, which you shouldn't. You're also asking if you should offer another option. Which you could, and in certain situations, should. So here's the thing: Back button You should never, ever, break the behavior of the back-button. At all times, you must strive to keep it's functionality in ...


4

If I understand the question properly then the answer falls into many different areas. You should be well read on the subject but I would recommend looking into a range of articles from the Gestalt School to Tufte to Nielsen to computer scientists looking into color and data visualization (as for example): Why Should Engineers and Scientists Be Worried ...


3

This seems to be more of a graphic design question than UX question. But there's something called "vertical rhythm" that might help in laying out the flow of elements on a page. Here's some references to get started if you're dealing with webpages: http://www.markboulton.co.uk/journal/incremental-leading ...


3

Setting default viewport size is typically used for responsive or mobile-optimized sites to prevent unnecessary resizing of the viewport because the webpage has been optimized for that particular viewing format. If you have a fixed width site that is NOT optimized for small screens. Then you really should not be setting a viewport size and allow the native ...


3

I think the crux of the issue here is that while web browsers were very good tools for navigating web sites in the past decades, modern web sites work in fundamentally different ways, and the browsers we use are no longer necessarily the best tools for navigating them. The simplest web site consists of a hierarchy of static documents with hyperlinks between ...


3

As several folks have commented on the question - it's a technical reason. However, as with most technical reasons, there are technical solutions (in most cases - secure apps are a whole different kettle of fish!). They're probably costly, slow or otherwise nasty in some way, but it's not an impossible problem. The real reason sites break the back button ...


3

I usually try to provide both on-screen back-button and support for browser back-button. Reasons: If the user is immersed in the flow of the app, an on-screen back button can help keep focus inside the flow and avoid losing the user's attention. Supporting the browser back button is important to me, even at great cost, because it's presumptuous design to ...


3

Colors should really match the theme of the site and be easy to the eye. For example, if the site is about valentines day, use shades of red and pink. Most importantly, make sure contrast is good. An example of bad contrast which many websites produce is light grey on white. Visit checkmycolours.com and put any URL in it to see if the website has good ...


3

It's a one-page responsive website. More descriptively, it's a one-page/long-scrolling responsive website with a hero shot, sticky header, and scrolling transitions. Let's break that down: One page refers to a site where the principle content narrative appears in sections on a single page rather than on different linked pages (as in a traditional ...


2

I would not show pricing for non-commercial customers on the page. Reasons: Those prices will be irrelevant to the vast majority of users. So it will just add unnecessary clutter and choice. The paradox of choice shows that having more choices actually makes it more difficult for users to buy, and you want to reduce, not increase purchase friction. Then ...


2

I'm not sure it's deliberately obscure, but rather a victim of circumstance. For example, the UX team's requirements might have been: We need to show how long ago a post/tweet was shared, as it creates a sense of immediacy and relevance We need to provide a link an individual post/tweet We need to cut down on UI clutter for the majority of users 99.9% of ...


2

For most web sites, it is very hard to justify breaking the back-button. Even shopping carts, bank money transfers, etc, can be made idempotent, so refreshing, back, then forward, etc doesn't cause unexpected behaviour. There are some scenarios where the back-button cannot be supported. For example, I worked on an extremely complex web application a couple ...


2

I'm coming from a web developer perspective, so I am a bit biased, but here's my two cents: Local domains are great, but hard to remember, if you're going to be using different countries, I would go with website.com/ca/mcdonalds. This actually makes it easier for other websites to integrate as well, as it is a simple RESTful interface. The /ca/ designates a ...


2

As this source suggests, this is the recommended markup: <map title="Breadcrumbs"> <a href="/">Home</a> > <a href="/foo">Foo</a> > <a href="/bar">Bar</a> </map> The links are part of the G65, which states: Breadcrumb trails are implemented using links to the Web pages... The ...


2

The recommendation is typically to go responsive. Barring that, there is no one recommended size. That's something you need to decide based on your users' needs, the context of your site, your business needs, etc.


2

The first option will fail when the user has enough files to put the "+" button below the fold. The second option doesn't suffer from this flaw, although it could benefit from a call-to-action heading, e.g. "Add a new item"


2

Allow direct editing of the columns headings. Allow direct editing as much as possible. Make the initial table creation as quick and easy as possible but understand this initial creation will likely be modified many times. So to create a table requires 2 numbers, number of rows and number of columns. Then show the table and let the user work on a "live" ...


2

So I actually did my Masters thesis research on the default zoom level and level of detail that users prefer when working with way finding and identification tasks. Overall, users tend to prefer a large scale map (more zoomed in) and a generalized view (as opposed to satellite imagery). However, there are exceptions to this. When setting the initial zoom, ...


2

Most travel websites suck when it comes to anything other than single guests or couples, especially with children. In many cases, you have to special case kids even more: Infants usually don’t count, but may require a crib. Toddlers may stay for free if sleeping in bed with their parents, but sometimes have to pay for breakfast, though probably not full ...


2

Consider how AirBnB shows the maximum number of guests allowed in a location. They start by asking the user to put in their number of guests. If it's missed here, the user can change it on the next screen, where they have the same dropdown as on the previous search. This time though, the results will dynamically update as the user changes their number of ...


2

There is no general rule However, here are some concepts and approaches that UX designers use. You may want to look up these terms to help you think through layout: UI or UX layout White space or breathing space. Grid alignment OS guidelines (look for layout metrics for iOS, Android, Windows, for example) This set of terms should help you get started.


1

Depends on the relation between the title and the columns, I'd say. If your title also covers the second column, then the visual hierarchy should reflect that, i.e., you should follow (2). If the title is not related to the second column, approach (1) is right. As an example, if the title says "Search Results for XYZ", and the second column contains ...


1

I don't think this is an area where UX design patterns are going to be helpful, because this isn't a well defined enough user flow that a reasonable pattern can emerge. That said, if I were designing this app and looking for helpful examples, I would assemble a taxonomy of something like the following sites: Banking and payment sites which offer ...


1

Predictable placement is important for common tasks If creating files is important (as it is for most sites of this nature), then it's important that users know instantly where to navigate to create a file. If you add the create widget to the end of a list, you are forcing the users to hunt around for it, which can be very frustrating. For frequently ...


1

Why couldn't OAuth and a fake name coexist? Use OAuth to set up an account for each new commenter. Keep the information acquired during the OAuth private, for your own use only. Then let the user create a fake name which they can share with the community. Best of both worlds? Also, while you're getting the OAuth Authorization, be sure to acquire Facebook ...


1

First and foremost: You should think about satisfying the needs of your users. No SEO argument should stand in the way of providing them with the tools they need. With that in mind: Breadcrumbs do highlight important keywords for search engines but most importantly they act as secondary navigation and help users know where they are within a website ...


1

A URL must uniquely identify a page. This is simply a basic principle, and you should discard any option that breaks it. Note the requirement you mention in your question: I need the businesses to be able to post the URLs of their pages... It won't be acceptable to businesses if the only available URL goes to a page where the user selects from ...



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