New answers tagged validation
2
As JohnGB said, this is really a security precaution. However, there is an alternative way which is usable and secure at the same time. Rather than sending back the password mypassword, you can:
Send back a hidden field indicating the password is saved on the server (hashed, of course).
In the password field, assign the value ********.
The user will see ...
3
The simple rule is that a password should never be stored in a retrievable format.
To be able to leave the password fields as they are, the password would have to be stored somewhere locally in a readable format - somewhere like the browser cache or a cookie. That is poor security as someone could later retrieve the password from one of these sources.
...
0
In my experience, when I still have no clue on how tech-savvy will these users be, a balance between the two is best.
However, I must admit I tend to use placeholders. Also, whenever I can (when there is only one or very few input fields), I choose a suggestive design and then limit user input.
I try using placeholders as a way to show what is valid and ...
0
If an input field has limited length or limited allowed characters, I would have some kind of client side validation for it, that would show immediately if the input doesn't match the format or exceeds the max length.
I've had to tackle/see others tackle so many typos/incorrectly formatted data from database rows, because there's been input fields without ...
2
I prefer to let the user type and somehow indicate the error with a formatting or length indicator. Twitter is a good example.
The benefit of this approach is particularly apparent in message entry fields where the user might just need to get their thoughts down then edit for length. In the case of data-centric fields (like phone numbers) it simply avoids ...
3
My recommendation would be to go with the email approach. That would be a one click process and it's already used by companies like TripIt to build up travel itineraries.
Other than that, I am not sure if you can insert text into the email sent by the online store, but if you do have access, you can have a simple text link which says:
"Copy the text of ...
1
I don't know the answer to your first general question, is it a technical concern?
Regarding 1: Since it's an either/or option you shouldn't present UI elements for both text and image selection at once. Instead use some button in each cell that indicates "insertion", like so:
and then show a popup menu action sheet with options for text, camera or camera ...
1
You do not need the list of error and you already know why : since [the user has] the error below the input. Exactly.
You feel right the shorter the form appears the better the conversion rates simply because nobody likes forms and especially not long forms (long meaning lots of input).
That said, the success feedback does not have to be on the page: you ...
2
Don't give trivial feedback, as it would take attention unnecessarily.
However, there are fields that a successful input in not trivial.
One good example would be the username. When you type your new username, there's a chance it's taken. When a proper one is entered, you can indicate that the chosen username is valid.
And another nice example (though ...
6
The user must feel that they are in control of the form and they should be aware how long the form is.
If it's a long form you can have titles at the top or the side marked as "sections" or "steps" and change the color (or change the font color)once they have been completed, like the example below that shows that the user is in screen 3.
But also you can ...
2
I would say that it's probably a good idea. If I run an installer on my OS, each step that is completed gets a verified icon filled until all steps are done. Although, notice on the screenshot that it's not a big green check box - I still get the feeling of "everything is allright".
Another advantage of this is that I can see how many steps there are to be ...
-1
Once is enough. Actually email-add for some is quite irrelevant for any confirmation. Specially on confirmation mail. Tons of disposable email adds are available on the web.
1
Here's a hypothetical to consider.
Let's say your signup page gets 500,000 visitors and a 20% conversion for 100,000 signups a year.
Without an email confirmation field, reasonable estimates say 0.4% (or 400) of these users enter the wrong email address. With email confirmation, a generous estimate says that drops to 0.1%. So the net loss is 0.3% (300 ...
0
Browsers are pretty awesome nowadays. Working with typed inputs is a good idea, however they don't provide a consistent UX, what you're maybe looking for. HTML5 support on typed inputs is being adapted by the browsers, but some of the controls are cumbersome. They don't provide validation, they don't provide clues for the user.
Also choosing the right ...
Top 50 recent answers are included
