UI mock-up - Account Setup Rev.2

Eyal Rozenberg eyalroz at technion.ac.il
Mon May 13 16:48:04 UTC 2019

I appreciate everybody's ardent work on the UI, but - don't you think
the UI discussions belong on some bugzilla page rather than on this
list? There are lots and lots of posts and comments which are rather
specific/minor. If it were me I'd make an initial post here calling for
comments/suggestions someplace else, with a link to that someplace else.

In general, once something is well-defined enough technically, and has
limited "macro repercussion", we should perhaps consider whether to
continue discussing it on this list or continue the discussion elsewhere.

Again, much respect for the UI design work!

On 02/05/2019 9:40, alex wrote:
> Hello folks,
> Here's an updated version of the account setup workflow.
> https://presentator.ura.design/en/XP9IsbuQ?v=0&s=1&m=preview
> <https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpresentator.ura.design%2Fen%2FXP9IsbuQ%3Fv%3D0%26s%3D1%26m%3Dpreview&data=02%7C01%7Ceyalroz%40alumni.technion.ac.il%7Cb9253ac615614332695a08d6cec90897%7Cf1502c4cee2e411c9715c855f6753b84%7C1%7C0%7C636923760179416062&sdata=TpqqsVIOksjURaN97puHutWp%2B8LZHiWKIMnDx6uRLU0%3D&reserved=0>
> *First Screen*
> I created 2 variations which we could use for some A/B testing. We could
> potentially release the version with a smaller and less prominent "Get a
> New Email Address" first, to later than replace it with a more prominent
> button once we have those potential providers partnerships.
> A tabbed system will be used to show the user the proper info and fields
> of what they selected, and a "Other" option which will open less common
> actions. This might seems like a bit of a stretch, but I'd like to
> pursue the idea of having a unified "Account Creation Dialog", no matter
> if the user needs to create an email, add a calendar, an RSS feed, etc.
> The location and experience should be consistent to prevent unnecessary
> learning curves or visual inconsistencies between sections.
> This section will be pretty modular, so there's no need right now to
> list which service/feature should or should not be there, since we can
> change them pretty easily and we will discuss those in a dedicated
> bugzilla tickets.
> *Error messages*
> To increase consistency and get the user comfortable with our paradigms,
> we should use the same notification style for warnings and errors we're
> currently using in the upcoming TB 68.
> Using the new notification system and color scheme will make the
> messages feel more prominent and readable. We should also make those
> messages selectable, so the user can copy the errors for a web search.
> *Manual Configuration*
> This is tricky since there are many fields and it's really easy to
> overwhelm the user.
> Splitting the "Incoming" and "Outgoing" fields in 2 tabs will help us to
> visually streamline what the user needs to input, and also will prevent
> the dialog to grow too much.
> With this UI, we can keep the maximum height of the modal around 600px,
> which can fit on a 768px height laptop screen, and will help us prevent
> annoying scrollbars.
> A potential "Get Help" button could be positioned if the manual
> configuration is necessary, or if an error message is particularly
> technical. For example, if the user gets a firewall warning, or an SSL
> warning, we could set that button to open a specific page in our website
> where we list common errors and how to fix them.
> Cheers,
> -- 
> Alessandro Castellani
> Lead UX Architect
> _______________________________________________
> tb-planning mailing list
> tb-planning at mozilla.org
> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmail.mozilla.org%2Flistinfo%2Ftb-planning&data=02%7C01%7Ceyalroz%40alumni.technion.ac.il%7Cb9253ac615614332695a08d6cec90897%7Cf1502c4cee2e411c9715c855f6753b84%7C1%7C0%7C636923760179426071&sdata=x1zePJSyJJhh21G2LWz%2BwR%2F6LFBqQo66%2FxwB%2FidoFYc%3D&reserved=0

More information about the tb-planning mailing list