Tag Info

It is generally accepted (and well proven) that shorter forms are completed more often than longer forms (with all else benig equal of course). However there are exceptions where some information is expected by customers, and leaving it out leads them to question the validity of the form. 'Shorter = better' is a good starting hypothesis, but one that you ...

If you don't need the information (e.g. the emergency contact details) then why collect it? Every extra field on a form increases the burden on the form-filler (they have to at least scan it to see what it is), increases the chance of error (as mentioned on UXMovement) and reduces conversion (as JohnGB refers). As it is, I would suspect that significant ...

I would recommend determining the key fields which would have to visible at all times keep this in a separate section. The remaining fields can be shown using an accordion which may be viewed as the user needs to. This would allow the user to jump to any section at any time and expand and collapse the content and edit it as he needs by providing him the ...

As the above answer mentioned, if you don't need it why you collect it? And I want to expand on that can try to give you a better solution. Most of the time, you need those optional information because the user might need to use some optional features that would require those optional info. So the question is not "do you need the optional info," but rather, ...

First of all is there an need for you to show the unfilled fields in your view mode since the user cannot technically fill the details there. I would recommmmend going with either of these approaches : Dont show the unfilled fields if the user has no use for them - For example you might be filling out the address details and you might have a field company ...

You are really faced with two problems in these situations. The first is with usability, and the second is with business. If the information you are collecting has no business value, then you can get rid of it and "maximise" usability. Otherwise, you need to think again. I think the real problem comes with the traditional notion that most of us have about ...

Should there be seperate interfaces for editing public and private fields? No, I like the approach of having an explanation under. Perhaps you could steal the icons from facebook (eg, globe from facebook), but a hover for that icon wouldn't be that effective. Perhaps hover for the field (but hover, not focus). So, private fields with different ...

Two places you can improve on. 1. Microcopy: Izhaki's comments are spot on. I'll add to them. I don't know about public and private. They can mean different things on the web. How about Visible and Hidden or Visible Fields, Hidden Fields or Active and Disabled? Display on Leaderboard/Remove from Leaderboard. (replace Leaderboard with what you are showing ...

I have a few comments on your ideas: 'Save Fields' is not a great name, I think 'Save Changes' or 'Commit Changes' is better. If the user drags a field to the deleted bin, 'save Fields' doesn't make much sense (are you saving the fields that are to be deleted - eah?). The 'Deleted' bin is in no way showing deleted fields. If anything, it shows the 'To be ...

Here are couple of ideas, some of which you may have already. I would probably place Edit at the top since if it is at the bottom of the page and there are a lot of fields, it will be below the fold (users may not see it) and even if the users know it is there they will have to scroll. I think it is a good idea to display read only view with data if the main ...