Closed
Bug 699866
Opened 14 years ago
Closed 13 years ago
[Tracker] Registration flow is a bit too long and complicated
Categories
(Participation Infrastructure :: Phonebook, defect, P1)
Participation Infrastructure
Phonebook
Tracking
(Not tracked)
VERIFIED
FIXED
2012-09-12
People
(Reporter: aakashd, Unassigned)
References
Details
(Whiteboard: [UX][Re-Design])
Attachments
(20 obsolete files)
I went through the log-in process today and found a couple of issues in the flow. The attached screenshot shows some of the major issues present and possible solutions to the problems.
Issue #1: After confirmation, users need to click on a link to go to the log-in page
Issue #2: After initial log-in, users see a splash screen. It's not entirely obvious on what to do with the app after registration.
Comment 1•14 years ago
|
||
Good call.
BrowserID removes the need for email verification step.
CCing @cbeasley as she had some feedback on vouching flow with is somewhat related to registration flow.
@aakash from a product planning perspective, should this be a dependency of Bug#665373 or is this out of scope?
| Reporter | ||
Comment 2•14 years ago
|
||
It can be, but I think it's a bit out of scope. The use of BrowserID fixes some of the obstacles present in the beginning of the flow, but the Mozillians app needs to better handle what happens after initial registration (i.e. confirmation and initial login).
Comment 3•14 years ago
|
||
Would love to see some consideration for semi-automatic registration upon JS detection of the use of a URL in the name field, AJAXing in an hCard etc. Would greatly accelerate registration for a small but heavily Mozilla community overlapping set of people.
| Reporter | ||
Updated•14 years ago
|
Target Milestone: 1.3 → 1.2
Comment 4•14 years ago
|
||
tantek - can you point me to a site that does this? It sounds cool. I want to make sure I understand all the moving parts.
Updated•14 years ago
|
Assignee: nobody → cbeasley
| Reporter | ||
Comment 5•14 years ago
|
||
We're going with the proposal outlined here - https://gist.github.com/93148e13884b89c32f4b
This is going to happen in chunks and not in 1.2, so I'll move this out of the release.
Target Milestone: 1.2 → 1.3
| Reporter | ||
Updated•13 years ago
|
Assignee: cbeasley → bram
Comment 7•13 years ago
|
||
What’s notable in the proposed registration flow:
* The front and the register page will explain what, why, and how new contributors should join Mozillians. What’s the benefit? Who are the Mozillians? What will joining involve, and what will happen? Can user search for other users right away? Who will contact the user?
* A step for common areas of interest that new contributors tend to get started with. We can do this by identifying the top groups, and then putting those groups as selectors in the common areas of interest. If users don’t do this step, a “general” steward will still contact the user. But we want to encourage it, because if users have selected things they’re interested in, we can get stewards from specific teams to contact them.
* Areas of interest are translated to terms that are familiar to users. For example, Firefox technically belongs to the Platform team, and websites to the WebDev team. But new contributors know that they just want to help with “Firefox” or “websites”. They won’t know “platform” or “webdev”. So when users check the box, the text box below will automatically be populated with the words that Mozillians have used in groups.
* Finally, each group’s information is going to be displayed at the last page, with websites, code repositories, IRC channels, and steward’s profiles. It allows user to take initiatives via multiple channels: GitHub, IRC, website, email.
Comment 8•13 years ago
|
||
What’s missing in this wireframe:
Explanatory information on the joining process.
We can perhaps explain it using 1-2-3 steps, then answer really basic joining questions that new contributors might have.
For example:
* What is BrowserID?
* Which email should I use: my Bugzilla email? My spam mail?
* Who are all these people I should contact, and how can I contact them?
* What is IRC, and how is it used within Mozilla?
Comment 9•13 years ago
|
||
Things to note in this wireframe:
Most common groups (look for most used groups currently used in Mozillians) are presented as a check box, so new contributors are not presented with a blank canvas. The idea is to have a good set of defaults to get them started, and if that’s not sufficient, let them experiment with adding new groups via the text box (which will be less accurate – remember, they’re new).
Comment 10•13 years ago
|
||
Things to note in this wireframe:
When user check a box, the corresponding group will populate the text box below. Note that the group reflects the system that we’re using on Mozillians, and may or may not be the same as the check box labels. For example: Firefox belongs in the Platform team.
Comment 11•13 years ago
|
||
Things to note in this wireframe:
Every time the new contributor logs in, he will see this contact information. After he has been vouched for, this page will be replaced with the community directory and search interface. This is debatable, of course.
This wireframe might also be missing an interface to change groups that the user is interested in. I wrote “might” because this page may not appear for very long before the user is vouched by a community member.
But an example scenario, nevertheless: the user might not be interested in helping with websites anymore, and instead he wants to do translation projects.
Comment 12•13 years ago
|
||
Attachment #596099 -
Attachment is obsolete: true
Comment 13•13 years ago
|
||
Attachment #596101 -
Attachment is obsolete: true
Comment 14•13 years ago
|
||
Attachment #596103 -
Attachment is obsolete: true
Comment 15•13 years ago
|
||
Attachment #596106 -
Attachment is obsolete: true
Comment 16•13 years ago
|
||
Attachment #596111 -
Attachment is obsolete: true
Comment 17•13 years ago
|
||
Added FAQ below the email address field. The text is not finalized yet, but it summarizes all the things that I think we should address in the registration form.
Attachment #596582 -
Attachment is obsolete: true
Comment 18•13 years ago
|
||
Registration flow details: https://wiki.mozilla.org/Mozillians/Phonebook#Registration
Comment 19•13 years ago
|
||
(In reply to Bram Pitoyo [:bram] from comment #18)
> Registration flow details:
> https://wiki.mozilla.org/Mozillians/Phonebook#Registration
This link isn't working for me... is there a better link to use?
| Reporter | ||
Comment 20•13 years ago
|
||
Ah, here's the link:
https://wiki.mozilla.org/Mozillians/Releases/1.3/Registration_Flow
Comment 21•13 years ago
|
||
Attachment #596584 -
Attachment is obsolete: true
| Reporter | ||
Comment 22•13 years ago
|
||
un-assigning from bram and looking for someone to pick it up.
Assignee: bram → nobody
| Reporter | ||
Updated•13 years ago
|
Whiteboard: [UX] → [UX][Re-Design]
Comment 23•13 years ago
|
||
Posting the Registration UX from 1-4 (inline with Bram's wireframes). Aakash, John and/or Matej - reposting the copy etherpad here, if we want to make any revisions to copy: https://mozillians.etherpad.mozilla.org/registration-flow-copy
Comment 24•13 years ago
|
||
Comment 25•13 years ago
|
||
Comment 26•13 years ago
|
||
Comment 27•13 years ago
|
||
Comment 28•13 years ago
|
||
Comment 29•13 years ago
|
||
I *love* these new mockups, especially the various homepage states. Nice work Lee!
I agree. It's like biting into a york peppermint patty.
Comment 31•13 years ago
|
||
The text box in attachment 611006 [details] under “enter your own skils” will partially match a tag name or description.
| Reporter | ||
Comment 32•13 years ago
|
||
Lee:
These look great. There's a few copy changes in terms of exclamation marks, but I think we're good to go here and can move on to the next part.
| Reporter | ||
Comment 33•13 years ago
|
||
Here's the final PRD: https://wiki.mozilla.org/Mozillians/Phonebook/Registration
Updated•13 years ago
|
Component: mozillians.org → Phonebook
Product: Websites → Community Tools
QA Contact: mozillians-org → phonebook
Target Milestone: 1.3 → ---
Version: unspecified → other
| Reporter | ||
Comment 34•13 years ago
|
||
Hey Lee, can you e-mail me the assets/images for the carousel?
| Reporter | ||
Comment 35•13 years ago
|
||
This is far too large. Breaking this up into a tracker.
| Reporter | ||
Updated•13 years ago
|
Attachment #611006 -
Attachment is obsolete: true
| Reporter | ||
Updated•13 years ago
|
Attachment #597692 -
Attachment is obsolete: true
| Reporter | ||
Updated•13 years ago
|
Attachment #596600 -
Attachment is obsolete: true
| Reporter | ||
Updated•13 years ago
|
Attachment #611005 -
Attachment is obsolete: true
| Reporter | ||
Updated•13 years ago
|
Attachment #611426 -
Attachment is obsolete: true
| Reporter | ||
Updated•13 years ago
|
Attachment #572023 -
Attachment is obsolete: true
| Reporter | ||
Updated•13 years ago
|
Attachment #596580 -
Attachment is obsolete: true
| Reporter | ||
Updated•13 years ago
|
Attachment #611001 -
Attachment is obsolete: true
| Reporter | ||
Updated•13 years ago
|
Attachment #611002 -
Attachment is obsolete: true
| Reporter | ||
Updated•13 years ago
|
Attachment #611003 -
Attachment is obsolete: true
| Reporter | ||
Updated•13 years ago
|
Attachment #611007 -
Attachment is obsolete: true
| Reporter | ||
Updated•13 years ago
|
Attachment #596585 -
Attachment is obsolete: true
| Reporter | ||
Updated•13 years ago
|
Attachment #596583 -
Attachment is obsolete: true
| Reporter | ||
Comment 36•13 years ago
|
||
Moving to fixed with the last dependency now taken care of on dev.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Target Milestone: --- → 2012-09-05
| Reporter | ||
Updated•13 years ago
|
Target Milestone: 2012-09-05 → 2012-09-12
Comment 37•12 years ago
|
||
Bumping to verified - this went live long ago. Nicely done all.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•