New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reverse use of asterisks in App Mining qualification form #289

Open
markmhx opened this Issue Oct 18, 2018 · 5 comments

Comments

Projects
None yet
2 participants
@markmhx

markmhx commented Oct 18, 2018

Currently we use an asterisk to indicate fields that are optional, but we should use them to indicate fields that are required since that's standard.

screen shot 2018-10-18 at 11 38 44

@markmhx markmhx added the app-mining label Oct 18, 2018

@aulneau

This comment has been minimized.

Collaborator

aulneau commented Oct 18, 2018

I think it's pretty standard to only asterisk/declare the optional field if the rest of the form is required, generally it's agreed upon to be better ux to have only one optional indicator in place of many required indicators. https://www.formulate.com.au/blog/required-versus-optional-fields-new-standard

@markmhx

This comment has been minimized.

markmhx commented Oct 18, 2018

If we don't want to add the asterisks everywhere else, I like Luke's suggestion there to "just add (optional)" to fields that are optional.

An asterisk for "optional" IMO is super confusing since it's traditionally used to indicate required / the opposite.

@aulneau

This comment has been minimized.

Collaborator

aulneau commented Oct 18, 2018

Sure yeah! I think I avoided it because I had helper text on the label already, but 'optional' VS an asterisk makes sense

@markmhx

This comment has been minimized.

markmhx commented Oct 19, 2018

No worries, that makes sense. Perhaps we should remove the parenthesis mentioning examples since developers are likely to understand the field without them?

i.e. Public repository URL (optional)

@markmhx

This comment has been minimized.

markmhx commented Nov 7, 2018

Confusion about the current use of an asterisk for this field appears to have been reported here: https://forum.blockstack.org/t/private-repository-in-app-co-signup-form/6636

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment