Tag Info

New answers tagged

1

This start/end dates problem is quite common in UX. With accounting, for instance, there is often the invoice date and (payment) due date - but there users are often interested in days (period) rather than due date. Anyhow, your solution is not bad at all. You could add lines to create a better visual grouping between the fields and the icon. The obvious ...


0

There have been some nice developments to widgets since this question was asked. The old world Designers had to choose between placeholder only, label only, or label + placeholder. Each has disadvantages: Placeholder only is problematic because field meaning is obscured when it is filled in (see other answers). Label only is problematic because (1) the ...


0

Form fields can have both labels and placeholder text. These are two different things. All form fields should have labels. Not all fields need placeholder text. You can also position a label over the field so it looks like placeholder text, but is still an actual label. You can also hide the label and only show placeholder text, but that would be awkward ...


0

Observations: I agree it's awkward when controls just appear suddenly. You have two modes: historical and average, so checkboxes aren't a good solution because they are better at on/off interactions. Radio buttons or dropdown selects are not great options because they aren't mobile friendly. Given this situation, a button bar is a reasonable way to do ...


0

My answer is to try and treat login/registration forms as a different type of input form, because it has a specialized purpose and the guideline is really trying to provide general guidelines to form design so it won't necessarily have examples for all different types of forms. The important thing is to identify and document which form design guidelines you ...


1

This is a common problem, not only with Material Design but also with broader responsive design. In responsive layouts one cannot depend on screen sizes and scaling can only take you so far, so layouts tend to involve a lot of open space to allow for sizing tolerance. The good news is, Material Design recognizes this issue and incorporates a set of design ...


0

Trace typing cannot replace key-based entry methods because it does not have the capabilities that key-based methods do. In order to provide a smooth input experience, trace typing is generous in converting your swipes to words rather than precise. Thus it represents a "best guess" as to what you intended to type based on your action and on the words it ...


3

Trace typing isn't new. It was invented over a decade ago and was known as IBM SHARK. There are several crucial differences between current smartphone keyboards and the original concept: SHARK used a non-standard keyboard layout called ATOMIK. The purpose of this layout was to greatly reduce the number of mis-recognitions by making the shapes of common ...


17

Since you asked for data, the following answer on skeptics stackexchange has good references to two studies which conclude that there is no net performance advantage to using swype over conventional touch keyboards: http://skeptics.stackexchange.com/a/26471 The two studies are here: http://m.pro.sagepub.com/content/56/1/1591.full.pdf ...


4

The wikipedia page on Swipe states: The creators of Swype predict that users will achieve over 50 words per minute, with the chief technical officer (CTO) and founder Cliff Kushler claiming to have reached 55 words per minute. This appears to be based on company claims rather than actual evidence. However, even if we take these claims at face ...


4

Good question, but the Wolfram reference is terribly incorrect. The use of the period . in user interfaces is almost universal nowadays, and I would advise against trying to overload the comma. The spread of the decimal point is a pretty interesting case on the effects of globalization and technology. In this case, the broad standardization of global ...


0

Numeric Input Pattern, as suggested terminology from HTML5: http://html5pattern.com/ I see it as a Subset of a Numeric Input.


4

I am trying to come up with some common terms and definitions that are suitable to use for specification or design documents I don’t think i can come-up with a better suggestion than the one you mentioned "formatted' numeric input field" Its the best possible outcome and I don't think you should worry too much because its long, though you can make ...


14

The term used for these format-constrained inputs is masked inputs or mask input. Here is a demo which includes a broad range of masks (date, time, phone number, etc). If you Google 'masked input' you will find plenty more examples. http://igorescobar.github.io/jQuery-Mask-Plugin/ And a screenshot for posterity in case the link dies in the future. It ...


0

Showing both options is going to increase friction and decrease entry If apple people are more likely to hit the orange login button then only show apple input and a tiny link at the bottom saying "I don't have apples what do I do?" which will take them to a separate login page for oranges. If orange people repeatedly try and enter the number of apples ...


3

Is there any reason that this is not a two step process? Step one: Show a screen asking "What do you have?" Display two choices side-by-side with pictures and make them clearly click-able Upon clicking either apples or oranges, proceed to step two Step two: If apples then show a box with instruction "Please specify how many apples you have in the box ...


17

Thought I might login some fruits as well :) Having clear and descriptive labels is always recommended. So to answer your question directly: Yes you should ask as an input field with a more generic label invites ambiguity. Placing a clear label (in this case questions) above each control helps establish clear relationship between what you are asking for and ...


2

While the green text in your wireframe isn't strictly necessary, I think it is worth including for the sake of clarity. They provide clear calls-to-action and make it clear that there are two separate routes. To look at it another way, on balance, there are no significant costs to usability by including those headings but there are benefits. I also agree ...


8

Why not do something like this, since it's and either or situation. I'm not too sure why you have the login bit for what appears to me to be the same action: download bmml source – Wireframes created with Balsamiq Mockups



Top 50 recent answers are included