You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Create an onboarding header for the donation process #1095
When the user donates, they can move from signed_up_donating to donated. At that point, the header can show the finish signing up, which would transition the user from signed_up_donating to donated, correct?
Or would it be slightly different? The transition to donated happens immediately on donation. The finish signing up nagivates to profile editing (to set first and last name) and then continues with the normal onboarding flow.
Either way, that part needs some clearing up, but is relatively simple.
The more complicated part is the following scenario:
User tries to donate
They sign up and sign in, session redirects them back to donate page
They don't do anything from here. Maybe they kill their browser or something and sign back in later. Maybe they even change their mind about donating.
How to put them back into the regular sign up flow? Should the header have something like "I changed my mind, let me just continue with the regular sign up process"?.
Reopening because we would like to do this, but it is definitely going to take some work. The problem right now is that we have no sense of a user state that's "signed up and donated to project", just "signed up and donating to project". This hobbles any possibility of making this work.
From my other comments, I do agree with the header. Combined with less strict navigation enforcing if the signup/onboarding is not done yet, it would do some good.
Adding another state should not be difficult, but it sounds like the state would be about the same as "signed_up", so, for the sake of discussion, any thoughts on simply renaming that state to ready_for_onboarding or something along the lines.
Activity
begedin commentedon Mar 22, 2017
When the user donates, they can move from
signed_up_donatingtodonated. At that point, the header can show thefinish signing up, which would transition the user fromsigned_up_donatingtodonated, correct?Or would it be slightly different? The transition to
donatedhappens immediately on donation. Thefinish signing upnagivates to profile editing (to set first and last name) and then continues with the normal onboarding flow.Either way, that part needs some clearing up, but is relatively simple.
The more complicated part is the following scenario:
How to put them back into the regular sign up flow? Should the header have something like "I changed my mind, let me just continue with the regular sign up process"?.
I would suggest
joshsmith commentedon Mar 22, 2017
I think it might be overkill to do this in the short-term, so I'm punting and closing this issue.
joshsmith commentedon Mar 24, 2017
Reopening because we would like to do this, but it is definitely going to take some work. The problem right now is that we have no sense of a user
statethat's "signed up and donated to project", just "signed up and donating to project". This hobbles any possibility of making this work.begedin commentedon Mar 24, 2017
From my other comments, I do agree with the header. Combined with less strict navigation enforcing if the signup/onboarding is not done yet, it would do some good.
Adding another state should not be difficult, but it sounds like the state would be about the same as "signed_up", so, for the sake of discussion, any thoughts on simply renaming that state to
ready_for_onboardingor something along the lines.joshsmith commentedon Mar 30, 2017
Done now.