<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hello folks,</p>
<p>Here's an updated version of the account setup workflow.</p>
<p><a moz-do-not-send="true"
href="https://presentator.ura.design/en/XP9IsbuQ?v=0&s=1&m=preview">https://presentator.ura.design/en/XP9IsbuQ?v=0&s=1&m=preview</a></p>
<p><b>First Screen</b></p>
<p>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.</p>
<p>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.<br>
</p>
<p>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.</p>
<p><b>Error messages</b></p>
<p>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.</p>
<p>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.<br>
</p>
<p><b>Manual Configuration</b></p>
<p>This is tricky since there are many fields and it's really easy
to overwhelm the user.</p>
<p>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.<br>
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.</p>
<p>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.</p>
<p>Cheers,<br>
</p>
<pre class="moz-signature" cols="72">--
Alessandro Castellani
Lead UX Architect</pre>
</body>
</html>