Change Details

This spike involves the work of discovering interventions that have the //potential// [i] to increase how quickly mobile VE is loaded and `ready` for user input. This ticket is a follow-on to the work the Editing Team has done in the past [ii] in service of this same aim. === Stories - As a **newcomer** who is trying to make my first edit on mobile web using VE, I want the transition from tapping {nav Edit} to the interface being ready for me to starting making a change to feel fast/snappy and smooth, so I don’t lose patience and abandon the edit I'd been intent on making. === Done - [ ] A prioritized list of~3 concrete improvement ideas that //appear// to have the potential to increase the speed with which mobile VE is `ready` for people begin making a change - [ ] For each, estimate the time needed to implement each, what – if any – other teams implementing an improvement would depend on --- i. Emphasis on "potential" above as we expect additional work and testing would need to be done to evaluate whether the intervention is //actually// effective at decreasing load times. ii. E.g. [mw:VisualEditor on mobile](https://www.mediawiki.org/wiki/VisualEditor_on_mobile), T239676

This spike involves the work of discovering interventions that have the //potential// [i] to increase how quickly mobile VE is loaded and `ready` for user input. This ticket is a follow-on to the work the Editing Team has done in the past [ii] in service of this same aim. === Stories - As a **newcomer** who is trying to make my first edit on mobile web using VE, I want the transition from tapping {nav Edit} to the interface being ready for me to starting making a change to feel fast/snappy and smooth, so I don’t lose patience and abandon the edit I'd been intent on making. === Done - [x] A prioritized list of~3 concrete improvement ideas that //appear// to have the potential to increase the speed with which mobile VE is `ready` for people begin making a change - [x] For each, estimate the time needed to implement each, what – if any – other teams implementing an improvement would depend on --- i. Emphasis on "potential" above as we expect additional work and testing would need to be done to evaluate whether the intervention is //actually// effective at decreasing load times. ii. E.g. [mw:VisualEditor on mobile](https://www.mediawiki.org/wiki/VisualEditor_on_mobile), T239676

This spike involves the work of discovering interventions that have the //potential// [i] to increase how quickly mobile VE is loaded and `ready` for user input. This ticket is a follow-on to the work the Editing Team has done in the past [ii] in service of this same aim. === Stories - As a **newcomer** who is trying to make my first edit on mobile web using VE, I want the transition from tapping {nav Edit} to the interface being ready for me to starting making a change to feel fast/snappy and smooth, so I don’t lose patience and abandon the edit I'd been intent on making. === Done - [ - [x] A prioritized list of~3 concrete improvement ideas that //appear// to have the potential to increase the speed with which mobile VE is `ready` for people begin making a change - [ - [x] For each, estimate the time needed to implement each, what – if any – other teams implementing an improvement would depend on --- i. Emphasis on "potential" above as we expect additional work and testing would need to be done to evaluate whether the intervention is //actually// effective at decreasing load times. ii. E.g. [mw:VisualEditor on mobile](https://www.mediawiki.org/wiki/VisualEditor_on_mobile), T239676