Closed iamjessklein closed 11 years ago
Additional notes from today:
Since we have to build custom login for < 13s, it should be offered for the other types of users as well. Persona can be an option too.
The data to collect from students:
Additional user types:
Parental permission guidelines:
As per our conversation on vidyo this morning, I am assigning this to @andrewhayward to take a stab at making a clickable version of this user flow.
This is now deployed to the sandbox.
@andrewhayward In the parent sign up option, is the parent signing their kid up for them?
@iamjessklein @threeqube @andrewhayward Following up on Friday's stand-up // I am adding the flow for using a parent sign-in process as requested. It is following 100% the DIY model. I have included screenshots.
1.Choose an Avatar (include warning "please don't use a photo of yourself" )
3.Enter your parents email address + a password (DIY provides a password already, that you can edit)
6.Parent clicks on verification link that leads to "Activate Parent Account" page 7.Parent clicks on the sign option
-the end.
@threeqube My thinking was that would be two routes for parents, that ultimately converge:
Seems like I missed a bit out though, looking back at it, so it's not actually implemented how I had it in my head :(
@andrewhayward that is correct. This would mean that you would also get rid of the hyperlink on the sign in/up window for parents to sign up. Correct?
@andrewhayward and @iamjessklein Can we check back up on how log in user flow for < 13 and > 13 will work? We need to create copy around it.
c.f. lego magazine email notification to parent:
:icecream: that is a great reference. Yes lets loop back on this.
Here is the user flow for sign up:
@andrewhayward note that there are a few slight changes based on the conversations with our legal team in terms of requirements. I still need to mock up the sign up for parents. This flow takes into account the need for email notifications, however, does not provide the design for them.
:+1:
there's email pieces to do, but otherwise this is done.
@stenington and I took a stab at this, iterating on the work that @andrewhayward already incorporated into http://csol-wireframes.herokuapp.com/
After researching ( http://dl.dropbox.com/u/52395152/coppa.pdf) we came up with a list of common elements for this kind of work:
Ultimately this is the flow that we came up with:
Minimal Sign Up flow (with Persona):
(a) If signing up for learner account:
if < 13:
*if > 13:
Notes: Persona alternatives? IF we wanted to offer alternatives to Persona as well. Any service that provides the site with the user's email address would work. we could offer it for >13s and guardians. The email would become the email that is required for badge issuance/the email that an <13 reported as their guardian's email
Devil's Advocate: if we're storing usernames, passwords and a guardian email address for < 13s. why not store username, passwords and user email for >13s and guardians? i.e. why use persona at all?
The next step here would probably be to wireframe this one out and then @cmcavoy can run it by legal.