-
Notifications
You must be signed in to change notification settings - Fork 120
Request: add explanation of benefits to verification screen #5101
Comments
Concretely (and @mcomella please correct me if I've misunderstood) the ask is to consider whether we make it more obvious that this screen represents a mandatory step that the user has to complete, and why: @ryanfeeley I know you've wordsmithed this quite a lot already, any feedback on the above? |
I have no credentials for UX'ing, but I think I'd like to emphasize to the user, "If you don't verify, sync won't work!" which I don't feel the either the current implementation or the proposal above highlight. |
It's a good point. A lot of users will miss the Confirm this sign-in heading, and just see "To better protect" and assume it's an optional step. It's a mandatory step, and we can perhaps make that more immediately clear. @rfk @mcomella how about something like?
|
I like making it more next-action oriented, seems like a significant improvement. I wonder if we can be even more specific with something like "To allow access to your Firefox data...". |
I like this because it reminds the user what they're getting from this extra step. Rather than "confirm this sign-in" (as a user, what do I get out of that? Maybe I don't actually want to put in the effort to sign in anyway), the user sees "To allow access to your Firefox data..." (as a user, "Oh, I do really want to access my bookmarks from this browser/app, I should do what it says."). |
@rfk @mcomella Much preferred, and is only shown to Sync users, so we can be more specific. How about:
|
This WFM 👍 I kinda wanna A/B test it to see whether it really performs better...@shane-tomlinson how much hassle would that be for such a small change, given our recent improvements to experiment metrics? |
from mtg: closing it as a WONTFIX (from @ryanfeeley) |
@liuche and I are building a standalone Sync library for Android/iOS. When a user signs into their FxA, we need them to verify their account in order to access their sync data.
I'm concerned that, without an explanation about why verification is required (i.e. to get sync data), users will cancel their login after they entered their credentials but before they verified their account.
I propose that we could explain why verification is useful to the user on the verification page (e.g. "To grant the application access to your sync data, you must verify your account.").
@rfk mentioned that perhaps the wording could be improved and this information applied to all sync log ins and requested I open that possibility up to discussion here.
As a library, one alternative (or additional) solution could be when the user hits cancel to after logging in but before verifying their account, prompt the user with a dialog: "If you don't verify your account, will be unable to access your sync data. Continue?"
I'm not a designer so I don't know what's best for the library and wider sync. Any thoughts?
The text was updated successfully, but these errors were encountered: