Skip to content

Instantly share code, notes, and snippets.

@data-doge

data-doge/mvp-onboarding-flow-notes-raw.md

Created January 20, 2016 06:29
Show Gist options

  • Select an option

    Learn more about clone URLs
  • Save data-doge/87ad20572cf8c82bfa32 to your computer and use it in GitHub Desktop.

Select an option

Learn more about clone URLs
Save data-doge/87ad20572cf8c82bfa32 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
mvp-onboarding-flow-notes-raw.md

  • screen 2 - 4 are identical to the admin-invite-user-to-create-group flow

  • need to take existing forms and make them look good

  • eugene needs svg of new logo and name

    • but for now, just use header tags

  • admin flow:

    • user is created with given email address - and given a token
    • a dummy group is created (name is "New Group") and the user is added as an admin to it
    • an email is sent to the user, with a link containing their token

  • in both flows:

    • no matter how they get to screen 2, email address is in the url params, so that it can be added to the form
    • name optional field on screen 2, below password (for now)

  • differences:

    • completely new user added by an admin
      • they land on screen 2 (with button text "lets go") and then they land on screen 4
    • this flow: no confirmation token needed for user, they confirm by just being there wanting it

  • should any emails be sent in this MVP process

    • for now: no email
    • in future: maybe

  • in the semi-near future when we actually build and want to test screen 1, we'll do so on staging because we don't want tons of people to be signing up on something that might be sketchy

  • eventually derek wants to design multiple screen 1's and use google analytics to route to random one, so we can see which works best

  • update: ACTUALLY BUILD SCREEN 1, but just the top part, above the crowdfunding image

  • omit 'try demo' link

two flows for group creation:

  • flow 1: setting up a group via admin invite or front page (in both cases, new user)
  • flow 2: existing user, creates a group from within the app

proposed solution: different group setup pages for each flow and ...

  • if user tries to start group via the front page
  • they are redirected to log in page
  • after log in they are redirected to the flow 2 group page
    • simpler because, a uninitialized group doesn't have to be created beforehand

also, once we're done with this mvp onboarding flow, does the 'admin invites user' flow even need to exist?

  • separate card:
    • first, having a discussion about staying private-invite only until OG beta day
    • second, if we do decide to make publicly accessible now -- need to think about tearing old admin invites user to create group flow

already a user? btn on screen 2 is irrelevant (see above words)

  • comment out the 'you can change shit later' on screen 3

Q: if a logged in user visits front page, are they redirected to the app? A: logged in user should never see the front page

omit menu button in above screens for now

Q: when user logs out, what page do they land on? A: front page

need to make cards for both: (seems like derek has done this)

  • help cards
  • example project
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment