Hot answers tagged

9

I hope this answer this question, but this is my personal process: I use the font sizes in my PSD mockups for reference purposes only, almost as a 'relative' size. Then after Design is approved, along with the assets, I create a separate html / CSS basic file as a style guide (a bit like a style tile) where I define the real size for all fonts and see how ...


8

When you are choosing icons, they should be the same style with the rest of the interface. If your interface is glossy, use glossy icons. If its flat design use flat icons. The important thing is not to mix them. For example, if your interface has 3D shapes or elements, don't use 2D icons, because they contradict the look and feel. Also, the primary use of ...


6

Switching from 4 inches to 4.7 inches and then to a 5.7 inches phone, the major difference I have observed is the Travel. Even after getting used to, a person with an average size of the palm will still struggle to reach out to parts of the screen which are beyond reach. This might require several readjustments of the hand's grip to the phone to reach out ...


6

1. Use an existing convention Typically, the 'more' is represented by 3 stacked lines or 'hamburger' as designers call it... Sometimes, a set of 3 dots, horizontally- or vertically- aligned represents this, 2. Create a hybrid You can create some unique variation of this icon by combining your business brand with this universal web design symbol! 3. Do ...


4

The initial assumption is wrong: Regardless of their dominant hand, people seem to use their phone in their non-dominant hand as well, and vice-versa. An old question on Quora gives some insights on this: https://www.quora.com/Which-hand-do-you-hold-your-iPhone-in-when-using-it-one-handed There is no clear winner: dominant holds vary In addition, we hold ...


4

Density-independent Pixels Sounds like what you're looking for is Density-independent Pixels. Even though you might be working in @2x sizes, the final result is the same. The code will remain Font-size: 24px; on desktop and mobile. The higher density screens require specific solutions for visual elements such as images and icons, but not for the basic ...


3

Presumably it is emphasised as - if the entire interface is converted to French and you can't read any French - then it is impossible to reverse the action !


3

Please don't flip anything away from where a user planned to touch a second ago.. If a user sees the settings ≡ icon on the right top while holding the phone in their right hand and cannot reach it with right thumb, they might as well move the phone to the left hand and reach for the icon with their right-hand index finger. So it shouldn't suddenly move to ...


3

I'll agree with you, showing errors one by one could be really annoying and might have a negative impact on your business or users. A form is like a conversation with your users. Why not be a great communicator and use inline form validation that's delivered at the right place and at the right time? For example, take a look at Twitter's sign up form: In ...


2

I completely agree the content should not shift. I would put a message showing the "staleness" of the data, e.g. "Last scanned 10 minutes ago" or "Last scanned on 6/27 at 9:30" This gives the user the context they need to decide whether or not they want to trigger a manual re-scan (or helps explain why something they are looking for isn't shown- it is ...


2

I agree with other answers/comments that indicate that you'll want to keep with the consistency/theme of the OS, however I'm going to add some "food for thought". The trend of "modern" flat icons is good from the standpoint of simplicity however I feel that sometimes we throw away some usability factors like discoverability just to get a flat look. I ...


2

For the initial state, I would go with your suggestion to have placeholders like -Suit- and -Number-. This shows the user exactly what it is supposed to: the appropriate informational labels for the comboboxes and that a selection needs to be made. On a side note, I thought it would be cool to have this design: This would be the initial state. The ...


2

Any interaction is only useful if the target users understand it. I'd suggest making a quick and dirty prototype that just has the radial slider and asking users to input various values and see how they get on. You should also test inputting the same values using two sliders, two text fields with number pads, and any other methods you can think of that ...


2

All the gestures are hidden from the user until they either are taught them or accidentally discover them. Gestures have no affordance. Obviously it does not help if app developers don't follow platform conventions. Onboarding techniques and TV advertising (I am thinking Apple here) can help with education. From a design perspective gestures should only be ...


2

You could introduce some way to set a specific priority (an icon, double clicking the existing priority column, etc). If I need to move from 345 to 13, I double click the 345 and type 13, hit enter and that row zips up to position 13 (former 13->14, 14->15, etc). I would likely combine multiple solutions. Click and Type is good for setting a specific ...


2

Apple does this in several places. Perhaps they're focused on making actions easily reversible everywhere. It doesn't seem like language selection is an exception.


2

The more menu on a bottom navigation menu is actually a rather common navigation pattern. Yelp, Yahoo fantasy football, Band are a few apps just on my phone that use this navigation paradigm. There are pros and cons to any navigation approach, the main con of a bottom navigation bar being that it uses more screen real estate than say your typical off ...


2

Unfortunately, mobile Web browsers will not render pdf inside an iframe. The pdf mime type is handled by most Web browsers as a file to be downloaded. The only way you could make it work is to convert the PDF to an image format before hand so that it can be displayed inside one of your iframes. The mobile constraint makes it difficult to show both at the ...


1

In a word, no. There is no consensus on swipe actions in apps. To illustrate the lack of consensus, here's a quick list of some applications of swipe actions: (When I say "swipe right", I mean swiping from left to right.) Google Android notifications: both left and right for dismissing Android recents: both left and right for dismissing Android wear: ...


1

Google has something that might help you a lot. You can find the default and accepted general swipe gestures on mobile applications on the following link: Gestures Patterns by Google Users are really familiar with this kind of gestures and their actions.


1

As was pointed out in a comment, I would revisit the idea of using a multiline text field instead. I'm sure you can find a way to watch for changes -- for example, on Android, there's a TextWatcher class you can use. Another option is to make the field look like a text field, but open up a dialog when it is clicked. If you still opt for an edit button, ...


1

Assuming I'm understanding the situation correctly, I will propose a few options 1) the best interface, is NO interface.. by detecting the browsers user-agent, you can determine what type of system they are on (and POSSIBLY skip one of the tab bar selections). I understand that you may not be able to do this in ALL cases. It will be VERY rare that someone ...


1

To answer your question: Short answer - No. Longer answer - No, but would it help development if you provided more guidance? Not only will it probably help the team if you define some basic stylistic ground rules (do you even have a style guide?), and it will give you a sense of scale about how it looks and how it works. As a designer you need to have a ...


1

Maybe a tabular data table is not best way to display this information? Perhaps consider using the card UI metaphor where you can dedicate more space to data and their labels: Note: depending on the data, some information does not need a label because the data describes their purpose.


1

A few years ago I heard a talk by Cory Lebson, who has written about UX in disaster scenarios. Two of his articles are here: The Critical Importance of Web Usability in Disasters Lessons from Disaster Research


1

Human Error - James Reason Detailed description on how people 'process information' - and how this causes them to make mistakes. This is the book to read. I was going to mention Yerkes Dodson - but I see its in the paper you reference. "State Dependent Memory" is also worth looking up. And any number of articles on the interface design in nuclear ...


1

I have built several UI screens like this in the past, with a table summarizing some info, but additional details and/or editable settings per row. My preferred approach is to keep the table read only, but allow the user to click/highlight a whole row at a time. Clicking this row can then populate a nearby "Details" section with all the detailed info and ...


1

I clicked around with that radial slider in the link you provided and can tell you that I much prefer more standard methods of input (numerical input, horizontal sliders/range selectors, etc.). Why? Because a number range doesn't conceptually end where it begins as the radial slider shows. Furthermore, it tends to be a bit unclear how to update the range ...


1

Unless there is some internal requirement to use one system or another for bankers and traders, the fact that they are bankers and traders shouldn't be a consideration. They are people, and so the issue is more what's best for people. For navigation, ease of scanning and recognition should be your focus, more so than in most other forms of text. So, you ...


1

Michael, I was think the same for right/left hand user, please correct me if i am wrong flipping the entire interface to the other side Should not flip the entire interface because for understanding / reading the information/content we do not required either right/left hand, rather the languages which required to read from right to left, required vision (...



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