The proposal we'll be discussing as a team next week is copied below.

Proposal

DEISION TO BE MADE
In what order will the Editing Team plan to design, build, and deploy Edit Check on mobile and desktop? Simultaneously? Desktop followed by mobile? Mobile followed by desktop? Something else?

PROPOSAL
For the initial Edit Check (prompting people to add references when adding new content), the Editing Team will design and develop the mobile experience before doing the same on desktop.

This will amount to a workflow that looks something like the below:

1. Converge on the mobile UX
2. Consult with Senior Contributors to learn what assumptions the proposed mobile UX makes that might need to be revised and identify opportunities to improve the UX to increase the ease and efficacy with which they can review edits
3. Build a prototype that implements the mobile UX
4. Converge on desktop UX
5. Conduct usability testing of mobile UX
6. Consult with Senior Contributors to learn what assumptions the proposed desktop UX makes that might need to be revised and identify opportunities to improve the UX to increase the ease and efficacy with which they can review edits
7. Build a prototype that implements the desktop UX
8. Conduct usability testing of desktop UX

RATIONALE
The proposal to prioritize work on mobile first is built on the following assumptions...

• ~38% of the edits volunteers in SSA are making are made on mobile [i]
• If we assume nearly all editors start out reading Wikipedia, then we can assume the "next generation" of newcomers and Junior Contributors from SSA are going to be more likely to start editing on mobile, seeing as how mobile pageviews continue to be ~3x higher than desktop pageviews [ii]
• We need more accountability for building for mobile than we do for desktop because there are more reminders/accountablilty for desktop embedded within our current environment than there are for mobile
• Desktop and mobile will require different enough UX to make designing both simultaneously distracting
• The mobile and desktop experiences will require, and depend on, the same backend infrastructure and heuristics
• Designing for mobile will cause us to make decisions about the overall Edit Check flow and feel that will apply on desktop despite potentially getting expressed in different ways

i. https://superset.wikimedia.org/r/2284
ii. https://w.wiki/6EwT

The team is going to move forward with the proposal posted in T325787#8545572; we'll be designing and implementing the mobile Edit Check experience first with work on the desktop experience to follow.