In T414710, we will be running a survey that will appear when people abandon the mobile source or visual editing interface (web).

This task involves the work of identifying what (if any) facets of the survey UX we've converged on is not feasible given the current state of the QuickSurveys extension.

Decision(s) to be made

• 1. How (if at all) will we adapt the "Survey UX" to cope with the limitations of the current state of the QuickSurveys extension?

Learning objectives

• 1. What (if any) facets of the "Survey UX" (described below) are not feasible given the current state of the the QuickSurveys extension?

Survey UX

Target audience

• Wikis: en.wiki (for this initial survey run)
• Platform(s): Mobile web
• Account state: Logged in and Logged out
• Max edit count: ≤100 cumulative edits
• Editing interface(s): mobile VE & mobile source

User experience

When someone who is logged out or logged in [and has published ≤100 cumulative edits] abandons an edit session on mobile web after spending ≥2 seconds in either the mobile visual or source ready state, present them with a quick survey.

Notes

1. "Abandon" in this context refers to someone either 1) explicitly tapping X within the source or visual editor or 2) tapping/swiping to navigate back to the previous web page they were viewing
2. We will be defining the contents (read: questions and copy) for the survey in T414710

Survey metadata

• We will want to group survey respondents by:
  • Whether they abandoning their edit with or without making a change to the document
  • Experience level (read: cumulative edit count bucket)
  • Account state
  • Editing interface (source or visual)
  • Wiki
  • Edit session initiation method (section edit, full-page edit, etc.)

Done

• Responses to all "Learning objectives" and "Decisions to be made" are documented on this ticket.