Tag Info

Hot answers tagged

82

Don't start with choosing colors! 1. First, distinguish notifications from errors This is a common point of confusion with UX. Consider these two messages: Sorry, the app has crashed - This is an error, and should be highlighted as an error (i.e. pop up alert, dialog, red button, etc). You have rejected a date with Kate Upton - Although this sounds ...


42

I would recommend moving away from colour for confirmation messages in this case. I say this because it can be confusing for the user especially since you are using red and green for "Reject" and "Accept" so when they have successfully done an action moving from red to green can be disorientating and unworthy extra cognitive overflow. Take a look at ...


20

I find that the grey background with white text gives a very neutral feel and looks good on the eye as well. Unless it's good or bad, I would avoid green or red.


10

This is a bug with the Google UI, and not intentional. You were right to notice the distinction, but it shouldn't be used as any kind of example of good design. As of now (March 2015), Google is in the middle of a long process of migrating its apps and platforms to Material Design, and it will take a while before most apps are compliant. Material Design ...


8

The message indicates a successful action, so if you're using color cues, this message should use the color of success: green, in your case. The danger color (red, in this example) should be used when the user is about to do something destructive (e.g. "Are you sure you want to delete this?"), but the message you're asking about is for when the user has ...


6

Already there are couple of good answers urging you from moving away from colors. I do agree with them. Considering the color blindness/cultural relations, colors should always be used as a secondary mode of conveying any information. But then again, if you are working with an application which already has alerts for success, failure which are using color ...


6

I'm pretty sure it's because Drive is developped by another team than the team who's working on the Google account canvas. More a question of schedule/production rather than UX/UI thought I guess.


2

Don't cross the streams! Changing color schemes is different from outright reversal of the palette. For heat maps, color carries the principal information so reversing the color axis isn't a great idea unless you don't mind putting up with some customer confusion. If you want to migrate to a dark-light strategy you may want to evolve customers through ...


2

Technically, the upper and the lower part belong to two different software products. The upper one implements the UI to the user account, and handles the navigation. The lower part belongs to the current application. I assume they where created at different times. Between these, there was a change in the style guide used, regarding how to style tooltips. ...


2

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

The one place that I have seen this approach was in an tablet application designed for shop staff to place orders on behalf of a customer. In that context, the order details including a list of items added and the total value was given prominence and displayed all the time. The sales assistant could then browse/search for products through a panel that opened ...


1

I am taking the liberty of assuming column text is something related / in context to the content on the page. This brings to mind many news websites and how they handle content. Here are a couple of websites. New York Times and NDTV respectively. They provide a clean header area for title. It gives central attention to the primary content on the page. ...


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

This is a very common pattern in enterprise apps. You have different role- or policy- driven views into a common application and model. You can either use separate layouts, or the same layout. Both can be successful. For these user interfaces, templating and widget re-use is very important, because you can assemble layouts very quickly by dropping in ...


1

I don't have an authoritative answer BUT the two tool tips refer to different environments and Google's designers might have wanted to differentiate between them. The first, "plain," tooltip is for Google's main navigation section. The second, "styled," tooltip is for the individual app within the broader Google environment.


1

Your question is one that Intuit has put a lot of time and effort into putting into practice with its TurboTax UI, where parent activities are done first, and child forms take care of the rest. The entire procedure of necessary work has been (as far as I can tell without being involved in its design) ordered from parent-to-child. As you may realize, children ...


1

Put a "Skip Navigation"or "Skip to main content" Links first element before every thing on top of your pages. So the keyboard user will decide to let screen reader go through all navigation and other stuff or just skip to go to the main content. so you can use visuallyhideen class to make the link invisible for sighted people. ...



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