Tag Info

New answers tagged

0

It's best not to reload during a signup process, but sometimes it can't be avoided. There are many signup processes for even very mature sites (e.g. gmail, ebay, etc) which involve page reloads. What issues need to be addressed? Page loads create cognitive disruption to users. While you're filling in a form, the page becomes your universe so a reload ...


0

Is the user likely to have all the requested information on hand when completing the form? Consider changing the field labels.


1

To address your question directly: The conversion ratio of registration pages varies drastically between systems. First and for most, there's the gain/loss ratio - what do users get for registering? A registration form on lunch on a mobile TODO list can have a conversion rate smaller than 2% - there are many similar apps out there that don't ask you to ...


3

When asking the users for their personal details, you have to examine the use case and create a user story. Having the user journey at hand is very handy in this situation. Examine how the users are landing on your page. If someone was looking for a service and they landed on a page which does not seem to provide it, they will leave/bounce to another page. ...


1

Without knowing the specific details of what info you want to gather, a couple things come to mind: Be clear about what you are asking each question If a user thinks they are only being asked about certain info for marketing purposes, they may a) be less likely to provide the info and b) feel less positive about signing up for your site. Sometimes you will ...


3

Conscious Decision IF the main idea here is to force the user to make a conscious decision to provide or not provide a phone number then maybe you could integrate a radio button group into the control. Radio Buttons The first radio button could live alongside the text box for the phone number. Selecting this one would mean they then have to provide some ...


0

Firstly, put an '*' and some text indicating the field is compulsory and you'll have less need to present people with this unconventional validation. However...only make the field compulsory if (as mentioned be others) there is a strong business case for it. The other issue with your example is that some users may skip the phone number hoping they don't ...


0

This is very confusing I have to say, reminds me of the fuzzy logic. Well fuzzy logic is a nightmare for the user, as he would like the system to keep it simple. Also, the user probably saw one or two forms in his life, I guess not a single one behaved as you suggest above. Bottom line, there is no semi-required like there is no semi-pregnant.


4

Are you sure that you're sure? This is the question you ask your users with this type of strategy. Business goals From a business perspective the thinking is: Required field - we must have it. Optional field - provide at will. Users The way optional fields are seen by users is: I can either provide it or not. If the user is aware of what is ...


1

While I've seen it before, I much prefer the yellow highlighting on fields like that. We tend to go green and red for traffic lights, if you should do it, but don't have to yellow fits perfectly.



Top 50 recent answers are included