Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Invite flow #38

Merged
merged 1 commit into from
Mar 28, 2017
Merged

Invite flow #38

merged 1 commit into from
Mar 28, 2017

Conversation

xla
Copy link
Member

@xla xla commented Mar 21, 2017

Invite flow

To enable a better on-boarding experience we need a way to correlate users and their inviter. One way is to keep a list of invites of a user that stores a unique id (e.g. facebook id, or generate random identifier) which can be kept through until the invitee hits the signup. If the invitee signs up and the conenction to the inviter is preserved we can automatically create connections for those so they can hit the ground running.

API

To create an invite from the current user the following endpoint should be called. The key and value are entirely up to the caller to decide, but must match one of the key/value pairs in the social_ids of the invitee during signup. Given the Facebook id of the invitee is known:

> POST /me/invites
{
	"facebook": "1234"
}

< 204 No Content

Then during singup the same information should be provvided for the user.

> POST /users?invite-connections=friend
{
	...
	"social_ids": {
		"facebook": "1234"
	}
	...
}

@xla xla self-assigned this Mar 21, 2017
@xla xla added the draft label Mar 21, 2017
@hellozimi
Copy link

I think it would be nice to get a response on POST /me/invites including some kind of unique identifier which we can pass onto the deeplink url, or if I pass a randomized hash of some kind into the post body which can later be used in the deeplink to match the invitee with his/her BFF 💥.

@mstrengnell
Copy link

Checkez out. Bc of all the checks.
Also: Love the BFF 💥 reference. MVP

@xla xla changed the title Add high-level docs Invite flow Mar 21, 2017
@xla xla added wip and removed draft labels Mar 23, 2017
To enable a better on-boarding experience we need a way to correlate
users and their inviter. One way is to keep a list of invites of a user
that stores a unique id (e.g. facebook id, or generate random identifier)
which can be kept through until the invitee hits the signup. If the
invitee signs up and the conenction to the inviter is preserved we can
automatically create connections for those so they can hit the ground
running.
@xla xla removed the wip label Mar 28, 2017
@xla xla merged commit d688dda into master Mar 28, 2017
@xla xla deleted the invite-flow branch March 28, 2017 12:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants