We’re rewarding the question askers & reputations are being recalculated! Read more.

New answers tagged

0

Agree with the Hossein. Go for the labels on top of the textfields. It looks logic: label is a header, textfield is a paragraph. The developers will love it: universal solution for all screen widths.


1

between these 2 options I choose top one(aligned to top). But I suggest you to give up inline labels and use vertical top aligned label for fields. Checkout this link about designing good forms


2

In all of the music apps and websites I've ever used, the most pleasant to use component for this scenario has always been the spinner. This is a text box containing the exact value, with increment/decrement buttons next to it. You could use a slider but this takes up a little more space, and is difficult to provide fine-grained control unless you also ...


1

Even though most of the literature and articles on validation is in the context of form input, I think that you can pretty much handle most of them in the same way on widgets. For example, here is an article from the NNg group withe some guidelines on How to Report Errors in Forms that applies some of the concepts that you have described. The example where ...


1

I agree with Cristian. It would be better to show the input range of the text field at the beginning. Another way could be to specify the input range in the "Placeholder Text". Still, if the user enters invalid numbers, I would recommend highlighting the box with a red color. It's one of the Usability Heuristics to inform the user about the error clearly and ...


1

I recommend either to show the allowed range for the input from the beginning or do real time validation. It is bad UX to verify inputs only after ok is being pressed. For the second part you can let the use input a value that is not widthin range like 1760 or even 17000 but mark the input red and disable the ok button. This is where the shown allowed ...


0

A good way of achieving this is by keeping the form same, but just changing the buttons at the bottom. So, the (default) log in screen has two fields: 1. for entering email/login 2. for the password and two buttons: 1. log in - which makes a request to the server with the credentials above. 2. sign up for new account (see below). When the user ...


0

The way I interpret your scenario, you mean that a user of your system has to correct addresses for several people (not themselves) who've had undelivered mail. The only benefit the preview adds is a comparison to the wrong address in the same format. If that format, how it's printed on a letter / parcel is of importance, is important then I would say it is ...


0

There is a reasonable usecase for that kind of preview - and it's actually used on this very site: markup or special formatting/layouting. While I'm entering plain text in the textarea/form, I would like to preview what the actual answer is going to look like. The same rationale could be applied to your scenario. We're constantly looking for recognizable ...


1

I do not see any benefits of showing a preview of the address to the user, especially if no feedback is provided on why the first address was wrong. Please consider instead developing on form address validation that aids the user. ( Is the format ok ? , zip code exists within the city and country ? , is overall street name length ok ? etc. ) There are ...


1

Kristin, what are the typical years that users would enter into this field due its intended use? Based on that, you could come up with an algorithm that would automatically create a four-digit year when a user enters fewer than four digits. As an ad-hoc example, of these were years of birth, than you can safely assume that any year would be less than, or ...


2

It's quite an in interesting title that NNGroup decided to pick for this. Placeholders by themselves are never the issue If you scan the internet, most studies talk about the following things that make placeholder "harmful": Using them as replacements for labels This phenomenon became a common occurrence in the early days of minimalist approach in ...


0

I think placeholder attribute are used to represents a short hint (a word or short phrase) intended to aid the user with data entry. According to w3c on placeholder The placeholder attribute should not be used as a replacement for a label. For a longer hint or other advisory text, place the text next to the control. Use of the placeholder ...


Top 50 recent answers are included