Tag Info

Hot answers tagged

12

I think a much easier solution for the end user, since you say the list of choices is the same for every row, is to have the table with the last column empty, and then a separate list somewhere on the page, near the table- not a dropdown but a list with all choices visible at a glance - where clicking a name will add it to the row automatically. This way, ...


11

Problem I think there are several usability problems in current design. Wide single line input limits the way that note could be expressed (no paragraphs, no breaks) and makes the reading much harder. Interaction style is non-convenient, as note-taking area is disjoined from appropriate order. This creates jump-and-search behavior while taking a note, ...


9

A general principle for power users is that they appreciate efficiency and can learn almost any control you give them. This is fantastic from your point of view because it means you can focus your interface design on speed optimisations and cut a lot of distracting fluff. Let's break down your users' actual workflow for a moment. Check through form, ...


6

There are too many decisions to make at the same time on this. You should use JavaScript to progressively invalidate later choices, but maybe not in the way you were thinking. In a case like this, I would try to break it into steps and auto generate a much narrower form from the first choice. You can remove any illegal combination when you display the new ...


6

You normally design form fields to match the expected input. Do you have a maximum character count for this field? If so, you can display a countdown, decrementing that number as the user types, to provide them with real-time guidance on how wordy they are allowed to be, and also to circumvent the awkward flow of accepting their typing and then erroring out ...


5

What you are describing is a Combobox and has been in use for as long as I can think about GUIs. The concept has gained new momentum in the web with the further development of dynamic elements and web apps – most notably google's search box with it's suggestions-as-you-type. Chrome's "Omnibar" is, basically, the same thing: It's a text field you can type in ...


5

You could use your described system (hiding every entered character after input) but still showing every special symbol as in dots, slashes, underscores etc. giving the user the opportunity to check the length before and after those characters. Further I think it would be ok to show the TLD. Additionally - since you are using a touch screen - you could let ...


4

It seems that there are some conflicting views when deciding to use a bold field input label or not. “In this layout [with labels above the input fields], it’s advisable to use bold fonts for input field labels. This increases their visual weight and brings them to the foreground of the layout.”—Luke Wroblewski. However, in an eye tracking study ...


4

Without understanding what the actual data is it's tough to recommend how to collapse but chances are users don't need to look at all of these columns at the same time. In fact since there is a scroll right now they can't look at them at the same time so you could easily swap out the scrolling interaction with the ability to collapse columns. So, I'd do ...


4

This sounds like a data-entry task, and I think it should be treated as such. That is, assuming that this is a task that returns with some frequency. When being confronted with such tedious work, it makes sense to optimize for speed rather than being friendly for new users. That means that you can afford your UI being harder to learn, as long as it is ...


4

Since you have acknowledged that users have an email address that they would prefer you to use, just ask them for that preferred channel. Don't try and second-guess whether it's a daytime/work/home/throwaway address: use the address they nominate. That is, the "most appropriate classification" is simply Preferred.


4

Hear those crickets? That’s the sound of no guidelines for dense data presentations for any design language. There has been a need for such guidelines since GUIs first arrived, but there aren’t any I know of. For what it’s worth, I’ve been developing my own approach for dense alpha-numeric GUI presentations over the years, which I described at Coded, ...


3

The biggest problem I see with your current layout is the separation of content. It's very difficult to see the difference between your first time request to the one below it other than the repeating information. This will be even more difficult when viewed in a mobile browser. For the mobile version, I recommend separating the mobile view into two ...


3

There are a number of general methods that can be used, but they all fall into one of three categories. Reward them in some way for filling out the information. This site does it by giving you the Autobiographer badge, but you could do it by rewarding your customers in any way that is appropriate. Punish them by withholding some feature or ability until ...


3

It's no surprise that your users liked the old form better. It's almost always better for the user to see everything organized on one page at once, rather than one section at a time. This is because the user's eyes are always scanning and moving in various directions on the page and showing everything allows them to move through fields faster without ...


3

As we've designed a heavy-duty data entry forms (B2B/ERP) our case is probably different from the one stated, but it might shed some light upon it. Our users' interviews were inconclusive so we've decided to watch the users in action, take notes, measure occurrences of actions, and devise patterns of usage. On one form we had about 120 (!) fields. ...


3

You could provide markers beside the scrollbar to show where incomplete fields are in the form. You could also use this to indicate where the sections of the page are. download bmml source – Wireframes created with Balsamiq Mockups For inspiration/code take a look at the sausage.js library (example) and the Scrollbar of Contents Chrome ...


3

Here's an option: You could temporarily make the text box bigger. While active, you would increase the size of the text-box, turning it into a bigger area. Here's a quick mockup. Before overflow happens: When overflow happens: When a field has too much text: Or perhaps a bit more slick: Things of note: To make sure other elements in your design ...


3

how about using a data-entry tree like this http://www.csprousers.org/help/html/data_entry_tree.htm and this http://responsibility.motorola.com/web_help/scriba_12b_-_Remove_this_leaf.png http://responsibility.motorola.com/web_help/Scriba_XLM_Tools_Training/Scriba_-_Material_Data_Entry_for_Complex_Products.htm But this will again depend upon how much data ...


3

As a user, in most cases I don't trust parser that reads the sentence in such human language format. Most events I enter are appointments. Appointments are always important for me, so I always want to be 100% sure that it was added correctly. So if an application allows me to input my appointment like this, I completely ignore this feature and try to find a ...


2

I can't say I know of any research into this, but for me this would be a no go. It just isn't intuitive enough for the user. Perhaps a better solution would be to present the user with a drop-down in the first instance, if then the user cannot select an appropriate option, reveal an input field giving the user the ability to manually enter the relevant ...


2

I attended a seminar on this subject in regards to developing mobile apps: http://www.uie.com/events/virtual_seminars/buttons_a_hack/ Josh suggested employing techniques used in gaming. Specifically, coaching and level up concepts. Coaching essentially is a guiding a sequence of behaviors. "Click here to add a user"... once they create one, ""you have ...


2

Do multiple rows need to be visible at all? Otherwise why not just display one row at a time. Or get rid of the row abstraction all together. Show the information from a row and all possible choices for him to click and select from.


2

Frankly speaking, I'm a little bit confused: you have working solution, you have users with engrained habits, but you still want to use totally different solution because you think the screen is too crowded. User's habits should be respected. If, as developers, we ignore these habits, we risk violating people's expectations and creating mental ...


2

Some quick thoughts: Have two views: one to step through the tickets one by one, using the whole screen for a single ticket, and moving on to the next once an assignment is made, and one to give an overview of the assignments currently made. Both views have different use cases. Use something visual to represent the developers (like photographs). This makes ...


2

Horizontal scrolling is not OK when displaying data. Instead you need to implement data visualisation that reveals more the wider the viewport, and less the narrower the viewport. Implement drill-down techniques, responsive web design and adjust font sizes, white spaces, margins, paddings and borders to make your data understandable in any case. To do this ...


2

As there are a lot of data, it's important to minimize user's cognitive load. The data should be clearly structured in a meaningful way and manual input should be minimized (recall over remember principle). To support those requirements, you could: Develop templates for the typical cases. To mantain flexibility, allow user to add or remove data fields ...


2

Google Calendar uses a similar input field and I'm quite fond of it. Like Apple's Calendar, it shows a suggestion for how to input a value into it, making it fairly accessible to users. The difficulty with implementing one though is putting enough intelligence into the parsing that it can accept the vast majority of options and formats a user may try.


2

My answer is to first of all avoid have such data heavy applications. Can your functions be separated into a flow? Or do all these interactive elements need to be presented at the same time? Can you separate the administrative UI and the presentative UI? I would focus my work on trying to reduce the number of items per page, since there's only so much you ...


2

@MichaelZuschlag hits the nail on the head: there are no matching guidelines for metro, and at least I've never seen any (platform-wide) for any platform. At first look, the intent of the UI formerly known as Metro is at odds dense UI. A "dense" screen would have to be broken up into detail pages (see Navigation guidelines). Your first screen would have ...



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