Skip to content
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

Use simpler/less-technical wording and UI. #521

Merged
merged 9 commits into from
Apr 28, 2023

Conversation

dd32
Copy link
Member

@dd32 dd32 commented Feb 14, 2023

This draft PR contains a lot of textual changes, which overall simplifies the language (See #516) but also the UI. This was mostly an experiment for myself in context of potential simplification for non-technical users.

Before After
Profile page Screenshot 2023-02-14 at 4 26 19 pm Screenshot 2023-02-14 at 4 26 07 pm
Login with a singular alternative Screenshot 2023-02-14 at 4 27 13 pm Screenshot 2023-02-14 at 4 37 41 pm
Login with multiple alternatives Screenshot 2023-02-14 at 4 26 31 pm
Screenshot 2023-02-14 at 4 26 38 pm
Screenshot 2023-02-14 at 4 41 02 pm
I don't love the stacked buttons, but i equally don't love the hidden list.

The buttons are a bit much, especially with multiple of them, so I also experimented with keeping the existing grey text:

Single Multiple
Screenshot 2023-02-14 at 4 36 11 pm Screenshot 2023-02-14 at 4 42 26 pm

It's obvious why the expander list was chosen when multiple other methods are enabled, but it doesn't provide a better interface, only a slightly cleaner one. I also now wish I hadn't kept with the capitals in the sentences, but I've made the screenshots.

@jeffpaul jeffpaul added this to the 0.8.0 milestone Feb 15, 2023
@jeffpaul
Copy link
Member

I concur that the buttons are a bit much and that the grey links "looks better". A slight tweak to capitalize Code in Emailed Code to match the case of the other two links would make things look "more similar" on those.

@jeffpaul
Copy link
Member

An alternative to the experimental designs here could be to mimic how GitHub handles the alternate methods. Specifically meaning in a second rounded square section with context updated to our methods:

Having problems?

GitHub example screenshot:
Screenshot 2023-02-15 at 2 47 50 PM

@ironprogrammer
Copy link

@dd32, the simplified text on the profile page example reads much better! 👍🏻

I like how @jeffpaul's GitHub example more clearly delineates the alternates. It's a stronger implication to "try these instead." Using TOTP seems better than burning a backup code. For this reason, it may not be a bad thing for the language to hint that the alternates are for when they're having trouble with TOTP 🤷🏻.

@paulschreiber
Copy link
Contributor

The term "U2F" is no longer used and the technology has not been supported in browsers for over a year. Just "Security Key" is fine. See also #427.

@iandunn iandunn modified the milestones: 0.8.0, 0.9.0 Mar 6, 2023
@dd32
Copy link
Member Author

dd32 commented Apr 13, 2023

The term "U2F" is no longer used

Just noting that this PR doesn't touch anything related to U2F, the U2F references in the screenshots are simply due to #427 not being finalised yet.

@dd32
Copy link
Member Author

dd32 commented Apr 13, 2023

Rebased and re-merged this a few times.. Using the discussion above, I took a step back and came up with a simpler direction here.

  • Restored back to the existing alternatives-ui, but with minor tweaking to the wording and display.
  • Renamed 'Backup Codes' to 'Recovery Codes' to better suit their purpose.
Before After
Profile page Screenshot 2023-02-14 at 4 26 19 pm Screenshot 2023-04-13 at 5 03 25 pm
Login with a singular alternative Screenshot 2023-02-14 at 4 27 13 pm Screenshot 2023-04-13 at 4 56 43 pm
Login with multiple alternatives Screenshot 2023-02-14 at 4 26 31 pm
Screenshot 2023-02-14 at 4 26 38 pm
Screenshot 2023-04-13 at 4 55 57 pm

@dd32 dd32 marked this pull request as ready for review April 13, 2023 07:05
@dd32 dd32 changed the title An experimental PR to consider simpler wording and UI. Use simpler/less-technical wording and UI. Apr 13, 2023
@ironprogrammer
Copy link

@dd32 I like how these screens have evolved. Definitely more clear and consistent (with itself and with other 2FA flows I'm familiar with). Looks great!

@jeffpaul
Copy link
Member

I concur, this looks great and I don't see any reason to continue iterating. Would be fine by me to merge this in and we can iterate later with any community/user feedback.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
5 participants