New user flow

[LissaD]

Create flow for new user. Steps may include:

• how they find the app (email link?)
• signing up - what info do they need to provide?
• do we need to verify info (email/phone)?
• short tutorial/walkthrough
• start labeling
• badge for completing steps?

[frhino]

For steps:

• We should have a basic landing page url that all digital marketing (emails, slack messages, facebook, twitter) leads to. Landing page should be responsive for mobile or desktop and include a very simple CTA and app store badges for iOS and Google Play Store.
• Signup needs email address, name, age (optional for NSFW tasks)
• No verification for first iteration, unless process of setting up authentication enables this easily
• Yes to tutorial/walkthrough, a video on that landing page referenced above would be perfect
• before start labeling, find the project you're contributing to if not directed their from a link shared by project. That project link would be generated when admin creates project and activates it. First few slides/cards in a project would include instructions, examples, an overview of how the project is structured, the real world impact the work could have, and how badges are earned (let's not make too big a deal about badges at first)
• Start labeling, first 10 are known/labeled examples
• Badge for getting the first 8/10 correct, if <8 correct, prompt user to consult instructions, then serve 10 more known examples and check for 8/10 again.

[LissaD]

[LissaD]

Okay, just posted another version of the New User Flow. Let me know what issues you see!

[LissaD]

Notes from our discussion last week about the posted user flow:

A. In Step 5, what are we using for user authentication? We discussed OAuth, and OpenID, but in the end, I think we were leaning toward using a fingerprint biometric / pin number combo. Looks like I should add create password/pin to this this step.
B. Where do you come back to, when you return to the app to do more labeling? A screen that asks if you want to resume labeling? Or should we just plunge them right back into the label stream?
C. A never ending scroll of tweets to label can be demoralizing, so how should we artificially constrain the labeling? Limit it to 15 or 20 tweets? Or something else?
D. How do we bring them back? What's the incentive for people to come back to do more labeling? Push notifications? Emails? In-app awards? Will this be something that the admin has to do manually, or can this solution be automized?

[frhino]

Great points @LissaD!
A. I think a mock up can be done with a standard registration pattern at this stage. Let's keep it as simple as possible at first.
B. For our first iteration, do we need the app to remember state? Can a user choose to resume session or start with admin's current greatest need?
C. Great idea, but not for first iteration.
D. We need a way to track sessions by:

• what time of day they start
• how long do they last
• how many examples were labeled
• how many sessions has the user initiated

With that data, we can engineer rewards and incentives such as you suggest. But not first iteration.

[frhino]

E. Step 6 might be later stage feature. Right now, lets MVP this for simple admin/client, one instance of app for each labeling project (1 admin and n clients on one labeling project).

[frhino]

F. Steps 8, 9, and 10 is definitely a usability feature we want to include, but not first iteration.