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

Already on GitHub? Sign in to your account

Usability bug where it required 2 clicks of the mouse to register a participant #12

Closed
deepakjois opened this Issue Jul 19, 2012 · 3 comments

Comments

Projects
None yet
4 participants
Contributor

deepakjois commented Jul 19, 2012

Steps to reproduce:

  1. Filter list of participants to locate the participant you want to sign in
  2. Place the NFC card on the reader
  3. Click Sign-In Button and Verify that NFC ID appears

The problem is that the process is not complete yet, even though it appears to be so. There is one more step required.

  1. Click the Sign-In button again

This behavior needs to be improved.

Owner

jace commented Jul 19, 2012

The new button appears in the place of the old button to take advantage of Fitts's Law. Easier to click it when it's right under the cursor. I agree it's not intuitive though.

  1. Is it possible to reposition the mouse cursor from within a browser? If we could move the cursor to over the new button, it's visually more intuitive while remaining easy to click.

  2. Can the registration process be more keyboard driven? For instance, when tagging a photo on Facebook, when you type to narrow down the list of names: if the list reduces to one person, the checkbox is automatically selected. You can then press Enter to finish tagging.

    Similarly here, we could have a keyboard-driven UI where if the selection narrows down to one person, hitting Enter will complete the first part (reading NFC tag) and hitting Enter again will complete the second part (registration).

    Even if there is more than one person in the narrowed list, clicking the first time will read the NFC tag, and hitting Enter will complete the second step because the keyboard focus has been shifted to the correct button.

ashwan commented Jul 19, 2012

The text on the new button was the ID generated and the colour changed to blue. Neither of these made it obvious what the button did then. I assumed it would sign people out if I clicked it again (since I wasn't told otherwise.)

My suggestions for a mouse-driven UI:

  1. Button should initially say "Get ID" which is what it says when you're entering a new participant, so it makes sense to keep it consistent across the app.
  2. On getting the ID, button can change to "Sign in" and the ID from the card displayed to the right.
  3. Clicking the button the second time changes it to "Sign out"
Contributor

miteshashar commented Jul 16, 2013

Closing this as it is no more relevant, with the UI having changed.

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