User Experience Stack Exchange is a question and answer site for user experience researchers and experts. It only takes a minute to sign up.
Sign up to join this community
I have a website that keeps track of oranges OR apples. Is it better that I ask or just show the input.
Is the green text needed?
It's a 50/50 that they'll have oranges or apples, so I would need to show both inputs at once.
I'm dealing with very beginner users here, if they don't see where to put in their apples, they may not know what to do.
Having clear and descriptive labels is always recommended. So to answer your question directly: Yes you should ask as an input field with a more generic label invites ambiguity. Placing a clear label (in this case questions) above each control helps establish clear relationship between what you are asking for and the means by which it could be provided.
The second aspect you need to take into concideration is how the questions are formulated: If input fields can only accept apples and oranges (which I assume is the case) then the questions will need to reflect that, gain clarity and be focused on the task.
From your comment that suggests that your target audience had initially difficulties identifying what an input field is! Then, it honestly seems to me that this is an educational challenge and should be treated as one. So I would suggest the following to achieve best results:
Form Narrative : Make the form tell a story!
Test and refine
Why not do something like this, since it's and either or situation. I'm not too sure why you have the login bit for what appears to me to be the same action:
download bmml source – Wireframes created with Balsamiq Mockups
Is there any reason that this is not a two step process?
Step one:
Show a screen asking "What do you have?" Display two choices side-by-side with pictures and make them clearly click-able Upon clicking either apples or oranges, proceed to step two
Step two:
If apples then show a box with instruction "Please specify how many apples you have in the box below:"
If oranges then show the instructions "You must login before you can specify how many oranges you have"
While the green text in your wireframe isn't strictly necessary, I think it is worth including for the sake of clarity. They provide clear calls-to-action and make it clear that there are two separate routes. To look at it another way, on balance, there are no significant costs to usability by including those headings but there are benefits. I also agree that it is best to display both options at once for the sake of simplicity and since there is no sensible default.
If apple people are more likely to hit the orange login button then only show apple input and a tiny link at the bottom saying "I don't have apples what do I do?" which will take them to a separate login page for oranges.
If orange people repeatedly try and enter the number of apples they have then only show the orange login fields and a link saying, "Click here if you don't have oranges"
