### Upcoming research will be focused on ([brief](https://docs.google.com/document/d/1e8Y_k3Xb0Ok9VCw1K2qQtaQ9I8CY14Jp23VcYBiYhuY/edit?ts=5d763856) | [prep](https://docs.google.com/document/d/1sd2Wg-Sdb5PSb5EBD-5ElJk0a4PEASMi4WNzw1LSJ8E/edit?ts=5d767e26)):
- V3 reality check with a design prototype based [on the current visuals on Zeplin](https://app.zeplin.io/project/57a120b91998d8977642a238/dashboard?seid=5d6fe67df555509eede8dbe9)
- Some comparison to V2 is advisable (DH)
- How can we retain users? What do we need to do to keep them coming back?
- Level of information when onboarding new users to edit Wikipedia
- How interested are first time editors in what their contributions are all about?
- Do we need to provide a lot of background to get people going in editing Wikipedia?
- Or does the power of Suggested edits lie in a hands-on approach without too much info and the heavy backpack of WMF projects?
- How interested are first time editors in knowing exactly where their edits go?
- What’s the level of detail in communication that we have to provide?
- Evaluate additional future components that we’re thinking about, such as:
- Additional onboarding tooltips ([Example](https://www.notion.so/wikimediadesign/Inspiration-784964c217274c06934f0235c189ea66))
- Badges (RS will create mockup)
- Social components (RS will create mockup)
- Tip cards in the Suggested edits feed (as per Johan’s idea on Slack, RS will create mockup)
- General edit onboarding to Wikipedia ([Example](https://www.dropbox.com/sh/1l18dq7pd0ad62u/AABkUfTxr2NfL580zGZW-HZ1a?dl=0))
- In-app FAQ section (rather than a link to a page, RS will create mockup)