Just fired up the latest build, checking out the frontend.
Selected exit that doesn’t work is a bit awkward
As a user, I see the green bars which seems good, and the fact that the exit is “selected” and I feel that the exit should be working. But then I see the register button and I think it must not be.
Possible solutions would be to
- Use the green bars to signify “connected” instead of reachable. Sort the list to place reachable exits at the top, and set unreachable exits to 10% opacity
- Do not “select” exits that are not registered. If there is some backend reason to always have a selected exit, just don’t show it in the selected slot if it is not registered.
@Adam_Soltys I will post a wireframe of the new design in here
Getting failed validation before I type anything
This is not technically incorrect, but it makes me feel bad. Use one of the methods for making this nicer, such as not validating until after submit or similar. People have written about the many ways to do this: https://ux.stackexchange.com/questions/74531/form-validation-when-should-error-messages-be-triggered
@Adam_Soltys ping me when you’ve decided how best to do this, before you implement it.
Possibly successful registration attempt still looks like an error
After submitting an email, the first thing that I see is the red validation failure. This will be fixed in the issue above, but I also think that there’s a lack of explanation about what is happening.
@Adam_Soltys I’ll let you know when I have wireframes for a better version
Region error state looks broken
First of all, the progress bar should probably go away. Second of all, we should rewrite the error message. @Adam_Soltys ping me to brainstorm on that.
“Waiting for contact” is confusing
Apparently it is reachable. I think this state means nothing to the user. Maybe it’s just a matter of rewriting the status? @ttk2 ping me about this so that I can refresh my memory on what this state means.