well, let’s try to join our skills to make this form usable, functional and good looking!
There are actually a lot of questions in the form. The risk is that the user get “scared” from all of this questions. We can maybe suggest to the client if is possible to gather the most important informations in the application form and then allow the user to go fill further data in a second time, as a “Complete your profile” functionality.
If it’s not possible and so assuming that we can’t cut down fields, in my opinion we’ll have to split the form into pieces (or steps, as a wizard) and probably the best way to do that is by following the already existing scheme that the client sent us:
Step1: Basic Information
Step2: Health History
Step3: Current Habits
Before start working on this, It would be great if we can get more informations about the target user for this form, as for example age, sex, etc...
Anyway, I suggest to consider the option of spending some of our time and resources in making the form a little more engaging for the user; even if it’s a health-related application, it doesn’t mean it have to be boring! ;) We can consider for example managing some of the question with elements that are more "visual" than a dropdown field or a radio button. I’m also using some icons we can consider to use to enhance the aesthetics of the UI.
Anyway, to start working on this, I need some more informations like, for example, in the "Health History" section, how many illness/conditions are supposed to appear the the dropdown list for the first two questions? It’s quite important to know this information because, in case the number of answers is limited, I can suggest using a different representation that allows the user to have a better experience than the classic dropdown list. The same applies to questions like “how frequently do you exercise”, etc….
In the mockup I’m sending to you I’m assuming the way answers are collected, but I need to confirm with someone who already have this information (probably you or the Project Manager).
Error states: I suggest to use an inline validation for each field, so that the user can get feedback for the errors while he is filling the form and not just at the end.
I think this will not affect a lot the general performance, but for sure you can tell better than me if this is a viable option.
One more suggestion: I think it may help adding some examples as placeholder for some of the questions, for example in the question that is asking to list all the drugs that the user is currently taking, we can use a placeholder to simplify the user’s cognitive process of remembering which drugs is taking, by using some of the most used drugs.
For what concerns the adaptation to mobile, I suggest to think first on the mobile version, and then adapt it to the desktop version.
Hi John,
well, let’s try to join our skills to make this form usable, functional and good looking!
There are actually a lot of questions in the form. The risk is that the user get “scared” from all of this questions. We can maybe suggest to the client if is possible to gather the most important informations in the application form and then allow the user to go fill further data in a second time, as a “Complete your profile” functionality. If it’s not possible and so assuming that we can’t cut down fields, in my opinion we’ll have to split the form into pieces (or steps, as a wizard) and probably the best way to do that is by following the already existing scheme that the client sent us: Step1: Basic Information Step2: Health History Step3: Current Habits
Before start working on this, It would be great if we can get more informations about the target user for this form, as for example age, sex, etc... Anyway, I suggest to consider the option of spending some of our time and resources in making the form a little more engaging for the user; even if it’s a health-related application, it doesn’t mean it have to be boring! ;) We can consider for example managing some of the question with elements that are more "visual" than a dropdown field or a radio button. I’m also using some icons we can consider to use to enhance the aesthetics of the UI. Anyway, to start working on this, I need some more informations like, for example, in the "Health History" section, how many illness/conditions are supposed to appear the the dropdown list for the first two questions? It’s quite important to know this information because, in case the number of answers is limited, I can suggest using a different representation that allows the user to have a better experience than the classic dropdown list. The same applies to questions like “how frequently do you exercise”, etc…. In the mockup I’m sending to you I’m assuming the way answers are collected, but I need to confirm with someone who already have this information (probably you or the Project Manager).
Error states: I suggest to use an inline validation for each field, so that the user can get feedback for the errors while he is filling the form and not just at the end. I think this will not affect a lot the general performance, but for sure you can tell better than me if this is a viable option. One more suggestion: I think it may help adding some examples as placeholder for some of the questions, for example in the question that is asking to list all the drugs that the user is currently taking, we can use a placeholder to simplify the user’s cognitive process of remembering which drugs is taking, by using some of the most used drugs.
For what concerns the adaptation to mobile, I suggest to think first on the mobile version, and then adapt it to the desktop version.