This task involves the work of understanding the proportion of edit sessions that would see the fallback experience T239676 implements if presented at a range of load times.

Knowing this will inform the amount of time we define as needing to have elapsed between someone tapping edit and the fallback experience (T239676) appearing.

Decision(s) to be made

• 1. What – if any – adjustments will we make to the amount of loading time that will need to have elapsed before someone is shown the prompt T239676 introduces?
  • For now, we're going to leave the current 3 second loading threshold as-is for now and reconsider when we prioritize work on T349231.

Research questions

1. What proportion of edit sessions that involve mobile VE being loaded by default would see the fallback experience (T239676) if it were presented at range of load times?

Requirements

The below is very much a first pass and requires @MNeisler to review and refine before we consider it "scoped."
Using data from the most recent mobile VE A/B test, show the number and proportion of distinct edit sessions that load mobile VE by default and would see the fallback experience (T239676) were it be shown after the following elapsed loading times:

1. 0.5 seconds
2. 1.0 second
3. 1.50 seconds
4. 1.75 seconds
5. 2.0 seconds
6. 2.25 seconds
7. 2.50 seconds
8. 2.75 seconds
9. 3.00 seconds
10. 3.25 seconds
11. 3.50 seconds
12. 3.75 seconds
13. 4.0 seconds

Note: For this analysis, loading time is defined as the amount of time that elapses between when someone presses edit (init) and the editor is ready (ready).